Volumes |
|
|
|
|
Attaching Volumes |
1.navigate to Storage-volumes |
1.shows list of volumes |
||
Detaching Volumes |
1.navigate to Storage-volumes |
data disk should be detached from instance and detached data disk details should be updated properly(i.e Instance Name -detached and Device ID is null) |
|
|
Download volumes |
1.navigate to Storage-volumes |
3. download volume will fail with proper error message "Failed - Invalid state of the volume with ID: . It should be either detached or the VM should be in stopped state" |
|
|
Delete Volumes |
case 1 |
case 1: |
||
Create Volume |
1. Perform "Add volume" by provinding name, availability zone and disk offering details.(i.e go to Storage-Volumes-) |
volume should be created successfully and listVolumes should contain the created volumes. Database should reflects with new created volume details(volumes table) |
|
]]></ac:plain-text-body></ac:structured-macro> |
Test Case ID |
Test Case Name |
Steps to be performed to test |
Verification Steps |
Priority |
Test Case Type |
||
---|---|---|---|---|---|---|---|
1 |
Upload a data disk |
call upload volume API with following parameters
|
Upload volume is successful |
P1 |
|
||
2 |
upload volume when disk type is not compatible with hyper visor type |
call upload volume API with following parameters
|
Error should be reported |
P2 |
|
|
|
3 |
Upload a Volume when maximum volume for the account is reached |
call upload volume API with following parameters
|
Error saying max limit is reached should be reported |
P1 |
|
|
|
4 |
upload a volume having size greater than max allowable size |
call upload volume API with following parameters
|
Error saying size exceeded should be reported |
P2 |
|
|
|
5 |
upload a volume with same name as one already existing |
call upload volume API with following parameters
|
Volume is created successfully |
P3 |
|
|
|
6 |
upload a volume with the name that's already deleted |
upload a volume |
upload should be successful |
P3 |
|
|
|
7 |
upload data disk with different format for xenserver |
call upload volume API with following parameters
|
Upload volume should be successful for all the formats |
P1 |
|
|
|
8 |
upload data disk with different format for VMware |
call upload volume API with following parameters
|
Upload volume should be successful for all the formats |
P1 |
|
|
|
9 |
upload data disk with different format for KVM |
call upload volume API with following parameters
|
Upload volume should be successful for all the formats |
P1 |
|
|
|
|
upload data disk with different format for OVM |
call upload volume API with following parameters
|
Upload volume should be successful for all the formats |
P1 |
|
|
|
10 |
Attach a uploaded data disk |
call attach volume api with following parameter
|
|
P1 |
|
|
|
11 |
Attach the uploaded data disk with different format for xenserver |
call attach volume api with following parameter
|
Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format. |
P1 |
|
|
|
12 |
Attach the uploaded data disk with different format for VMware |
call attach volume api with following parameter
|
Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format. |
P1 |
|
|
|
13 |
Attach the uploaded data data disk with different format for KVM |
call attach volume api with following parameter
|
Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format. |
P1 |
|
|
|
|
Attach the uploaded data data disk with different format for OVM |
call attach volume api with following parameter
|
Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format. |
P1 |
|
|
|
14 |
List volume showing states of volumes |
call list volumes api |
Verify the response shows different states of the volumes likeNOT_DOWNLOADED, DOWNLOAD_IN_PROGRESS, DOWNLOADED |
P1 |
|
|
|
15 |
list volumes showing volume residing on secondary or primary |
call list volumes api |
Verify the response shows where the volume is residing |
P1 |
|
|
|
16 |
delete volume residing in secondary storage |
call delete volume api with volume id |
volume should be deleted |
P1 |
|