cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8394) Skip test cases through setUp() instead of setUpClass()
Date Wed, 06 May 2015 11:02:00 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530341#comment-14530341
] 

ASF subversion and git services commented on CLOUDSTACK-8394:
-------------------------------------------------------------

Commit 6c3dc15fcbf966d3ff626cf190d5ad8bbd06faf1 in cloudstack's branch refs/heads/master from
[~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6c3dc15 ]

CLOUDSTACK-8394: Skip test cases through setUp() instead of setUpClass()

Signed-off-by: Gaurav Aradhye <gaurav.aradhye@clogeny.com>
This closes #231


> Skip test cases through setUp() instead of setUpClass()
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-8394
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8394
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: Future
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: Future
>
>
> When the tests are skipped through setUpClass, the statement "raise unittest.SkipTest()"
is used. This is seen as exception in the logs. To avoid this, alternatively we can set class
level variable in setUpClass and read this variable value in setUp() and skip the test case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message