[
https://issues.apache.org/jira/browse/CLOUDSTACK-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950549#comment-13950549
]
ASF subversion and git services commented on CLOUDSTACK-6125:
-------------------------------------------------------------
Commit 91a5e3bb6634f9f0b98e7021fc55e680c6eba45f in cloudstack's branch
refs/heads/master from SrikanteswaraRao Talluri
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=91a5e3b ]
CLOUDSTACK-6125: adding 'selfservice','provisioning' tags to segregate the tests
that can be run on simulator only and that needs hardware.
> [Automation]: Segregate total TC's in to Self Service and Provisioning Test
> Cases
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6125
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6125
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Reporter: Santhosh Kumar Edukulla
> Assignee: Srikanteswararao Talluri
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> This bug is logged to track the categorization of all test cases.
> We have to go through all of the test cases and divide them into two groups:
> 1. Provisioning Tests: Tests that require actual hardware. (e.g. Start/Stop
> VM on ESX, XS, and KVM; Create/Remove rules on VR or network equipment;
> Create Snapshot on storage).
> 2. Self-Service Tests: Tests that tests our self-service business logic.
> Self-Service tests are tests for CloudStack’s business logic. It’s not a
> test of whether actual provisioning succeeded.
> VM placement
> Snapshot policies
> Resource limits
> Usage
> Resource cleanups
> Note: I have added an initial estimate to this case. As well, we need to do
> incremental segregation and have them reviewed parallelly with alex\abhi.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
