cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Aradhye (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-8278) Usage test path - Correct code flow in case the usage job timing is not to be set through test case
Date Wed, 18 Mar 2015 09:38:38 GMT

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

Gaurav Aradhye updated CLOUDSTACK-8278:
---------------------------------------
    Fix Version/s:     (was: 4.5.1)
                   Future

> Usage test path - Correct code flow in case the usage job timing is not to be set through
test case
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8278
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8278
>             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
>
>
> The flag "setUsageConfigurationThroughTestCase" dictates whether we should set the usage
related config from test case itself (And restart the management server and usage server in
the process) or not.
> When the flag is False (When we don't want to disrupt other test cases and/or usage server/job
is already configured), then it should be ensured that the code is broken anywhere. Set the
current date to cls.curDate variable in this case to avoid code break.



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

Mime
View raw message