You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Santhosh Kumar Edukulla (JIRA)" <ji...@apache.org> on 2013/10/28 06:51:30 UTC

[jira] [Updated] (CLOUDSTACK-4971) Verifying proper Setup Issues EX:Server Down, other prerequisites for test setup to minimize test script failures.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santhosh Kumar Edukulla updated CLOUDSTACK-4971:
------------------------------------------------

    Assignee: sadhu suresh

> Verifying proper Setup Issues EX:Server Down, other prerequisites for test setup to minimize test script failures.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4971
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4971
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>         Environment: Regression,Smoke tests etc.
>            Reporter: Santhosh Kumar Edukulla
>            Assignee: sadhu suresh
>
> 1, Currently test scripts are running despite the test setup has issues. EX: In one of the test scenario, where ldap server was down, then test suite depending upon them was still running. 
> 2, Ideally, the setup should check for these dependencies before running the test script and exit wherever possible with proper log and reporting .
> 3,  We may not be able to cover all setup issues, but the purpose of setup is also to check for its existence and dependencies. If scripts depending upon particular server conditions, should have a proper setup verifying the server existence before proceeding further. 
> 4, I believe running test cases when setup is down is also not idealistic. 
> 5. Purpose is to reduce script errors vs failures due to product bugs. 
> 6. Logging this bug to track the setup issue cases or script failures. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)