Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0B8F310818 for ; Mon, 28 Oct 2013 05:49:57 +0000 (UTC) Received: (qmail 88842 invoked by uid 500); 28 Oct 2013 05:49:54 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 88554 invoked by uid 500); 28 Oct 2013 05:49:44 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 88512 invoked by uid 500); 28 Oct 2013 05:49:40 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 88505 invoked by uid 99); 28 Oct 2013 05:49:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 05:49:39 +0000 Date: Mon, 28 Oct 2013 05:49:39 +0000 (UTC) From: "Santhosh Kumar Edukulla (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-4971) Verifying proper Setup Issues EX:Server Down, other prerequisites for test setup to minimize test script failures. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Santhosh Kumar Edukulla created CLOUDSTACK-4971: --------------------------------------------------- Summary: 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 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)