cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Kumar Edukulla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-6125) [Automation]: Segregate total TC's in to Self Service and Provisioning Test Cases
Date Mon, 17 Feb 2014 07:23:19 GMT

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

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

    Description: 
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. 






  was:
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.    






> [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.1.5#6160)

Mime
View raw message