cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-7203) Add try catch blocks in setUp() and setUpClass() methods in test cases and call tearDown methods explicitly in case we catch exception
Date Tue, 02 Dec 2014 19:37:23 GMT

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

Animesh Chaturvedi updated CLOUDSTACK-7203:
-------------------------------------------

BULK EDIT> As you know 4.5 is getting ready for release and these New feature and Improvement
tickets are still open, please update the status. If the changes are not committed yet then
these tickets need to be moved out of 4.5

> Add try catch blocks in setUp() and setUpClass() methods in test cases and call tearDown
methods explicitly in case we catch exception
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7203
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7203
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.5.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.5.0
>
>
> If exception occurs in setUp() and setUpClass(), then in that case cleanup does not happen
(tearDown method is called only when setUp is successful).
> Hence it is wise to catch the exception and call the tearDown method explicitly, so that
previously created resources get cleaned up and it does not affect the execution of the next
test cases



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

Mime
View raw message