You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Santhosh Kumar Edukulla (JIRA)" <ji...@apache.org> on 2014/02/17 08:19:19 UTC

[jira] [Updated] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases

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

Santhosh Kumar Edukulla updated CLOUDSTACK-6125:
------------------------------------------------

    Summary: [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases  (was: [Automation]: Bucketize total TC's in to Self Service and Provisioning Test Cases)

> [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 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.
> VM placement
> Snapshot policies
> Resource limits
> Usage
> Resource cleanups
> Self-Service tests are tests for CloudStack’s business logic.  It’s not a test of whether actual provisioning succeeded.    



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)