[
https://issues.apache.org/jira/browse/CLOUDSTACK-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377722#comment-14377722
]
ASF subversion and git services commented on CLOUDSTACK-8278:
-------------------------------------------------------------
Commit 54a4b2bad79321f241e97d19ce861dc0196ec946 in cloudstack's branch
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54a4b2b ]
CLOUDSTACK-8278: Usage test path - Correct code flow in case the usage job
configuration is not to be set through test case
Signed-off-by: Rohit Yadav <[email protected]>
> 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)
