| hypervisor : VMware | Abbreviation SO :service offering
CO :compute offering
| | | | |
Test Case ID
| Test Case Name
| Steps
| Expected Results
| Priority
(P0|P1|P2)
| Test Case Type
(Sanity | Functional|Upgrade|Performance)
| Automatable(Y/N)
|
|---|
1 | UI and API
| 1-Login through UI
2-Check for upgrade button
3-Select CO and Upgrade
| 1-Upgrade button should be present.
2- Should call scaleVirtualMachine and return job id
| P0 | Functional | Y |
| User VM CPU/ RAM scale up | | | | | |
2
| Scaling up CPU
(Capability available on current host)
| 1-Select a running user vm
2-upgrade SO
| 1- CS should upgrade VM with SO.
| P0
| Functional
| Y |
3 | Scaling up CPU
(Capability not available on current host but available in current cluster)
| 1-Select a running user vm
2-upgrade SO | 1-Vm should migrate(live) to another host
which is having capability.
2- SO should get upgraded | P0 | Functional | Y |
4 | Scaling up CPU
(capability not available in current cluster)
| 1-Select a running user vm
2-upgrade SO | 1-CS should not upgrade VM with SO. | P0 | Functional | Y |
5 | Scaling up RAM
(Capability available on current host)
| 1-Login through UI
2-Click upgrade SO
3-Requested resources are available on current host
| 1-CS should upgrade VM with SO. | P0 | Functional | Y |
6
| Scaling up RAM
(Capability not available on current host but available in current cluster)
| 1-Login through UI
2-Click on upgrade SO
3-Required resources are not available on current host
but available in current cluster
| 1-Vm should migrate(live) to another hos
which is having available resources
2- SO should get upgraded
| P0 | Functional | Y |
7 | Scaling up RAM
(capability not available in current cluster)
| 1-login through UI
2-Click on upgrade SO
3-Required Resources not available on current host
and also not available in current cluster | 1-CS should not upgrade VM with SO. | P0 | Functional | Y |
8 | Scaling up CPU and RAM
(Capability available on current host)
| 1-Login through UI
2-click on upgrade SO
3- Required resources are availableon host available | 1- CS should upgrade VM with SO. | P0 | Functional | Y |
9 | Scaling up CPU and RAM
(Capability not available on current host but available in current cluster)
| 1-login through UI
2-click on upgrade SO
3-Required Resources not available on host
4-Resource available in same cluster | 1-Vm should migrate(live) to another hos
which is having available resources
2- SO should get upgrade | P0 | Functional | Y |
10
| Scaling up CPU and RAM
(capability not available in current cluster)
| -Login through UI
2-click on upgrade SO
3-Required Resources not available on host
4-Resource not available in same cluster | 1-CS should not upgrade VM with SO. | P0 | Functional | Y |
| System VM CPU/RAM scale up( Need to repeat for SSVM,CPVM,VR)
| | | | | |
| Scaling up CPU
(Capability available on current host) | 1-Select a running user vm
2-upgrade SO | 1-CS should upgrade VM with SO. | P0
| Functional | |
| Scaling up CPU
(Capability not available on current host but available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-Vm should migrate(live) to another host
which is having capability.
2- SO should get upgraded | P1 | Functional | |
| Scaling up CPU
(capability not available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-CS should not upgrade VM with SO. | P2 | Functional | |
| Scaling up RAM
(Capability available on current host) | 1-Select a running user vm
2-upgrade SO | 1-CS should upgrade VM with SO. | P0 | Functional | |
| Scaling up RAM
(Capability not available on current host but available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-Vm should migrate(live) to another host
which is having capability.
2- SO should get upgraded | P1 | Functional | |
| Scaling up RAM
(capability not available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-CS should not upgrade VM with SO. | P2 | Functional | |
| Scaling up CPU and RAM
(Capability available on current host) | 1-Select a running user vm
2-upgrade SO | 1-CS should upgrade VM with SO. | P0 | Functional | |
| Scaling up CPU and RAM
(Capability not available on current host but available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-Vm should migrate(live) to another host
which is having capability.
2- SO should get upgraded | P1 | Functional | |
| Scaling up CPU and RAM
(capability not available in current cluster) | 1-Select a running user vm
2-upgrade SO | 1-CS should not upgrade VM with SO. | P2 | Functional | |
| | | | | | |
| Restart/power off VM during operation | | | | | |
11 | Restart VM while scaling UP CPU
| 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
4- Required resources are available on current host . | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering)
| P1 | Functional | Y |
| Restart VM while scaling UP CPU | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | Functional | |
| Restart VM while scaling UP CPU | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
3-Required resources are not available on current host
and not available in current cluster | 1-Should not get upgraded
| | Functional | |
12 | Restart VM while scaling UP RAM
| 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4- Required resources are not available on current host
but available in same cluster
| 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | P1 | Functional | Y |
| Restart VM while scaling UP RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP RAM | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
3-Required resources are not available on current host
and not available in current cluster | 1-Should not get upgraded | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
4- Required resources are available on current host . | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are not available in cluster. | 1-Should not get upgraded | | | |
| Restart/power off system vms during operation( Need to repeat for SSVM,CPVM,VR )
| | | | | |
| Restart VM while scaling UP CPU | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
4- Required resources are available on current host . | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP CPU | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP CPU | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are not available in cluster. | 1-Should not get upgraded | | | |
| Restart VM while scaling UP RAM | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
4- Required resources are available on current host . | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are not available in cluster. | 1-Should not get upgraded | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-click on upgrade SO
3-Use API to restart VM
4- Required resources are available on current host . | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are available in cluster. | 1-DB should get updated with new compute offering
2-When Vm started it should use those values(new compute offering) | | | |
| Restart VM while scaling UP CPU and RAM | 1-Login through UI
2-Click on upgrade SO
3-Use API to restart VM
4-Required Resources are not available on current host
5-required resources are not available in cluster. | 1-Should not get upgraded | | | |
| Snapshot creation while scaling up CPU/RAM | | | | | |
17 | snapshot creation while scaling up RAM
| 1-Login through UI
2-click on upgrade SO
3-click create snapshot
4- Required Resources on host available | snapshot creation should fail
| P2 | Functional | Y |
18 | snapshot creation while scaling up RAM | 1-login through UI
2-click on upgrade SO
3-Click create snapshot
3-Required Resources not available on host
4-Resource available in same cluster | snapshot creation should fail | P2 | Functional | Y |
19 | snapshot creation while scaling up CPU
| 1-Login through UI
2-click on upgrade SO
3-click create snapshot
4- Required Resources on host available | snapshot creation should fail | P2 | Functional | Y |
20 | snapshot creation while scaling up CPU | 1-Login through UI
2-click on upgrade SO
3-click create snapshot
4- Required Resources not available on host
5-Required resource are available within same cluster
| snapshot creation should fail | P2 | Functional | Y |
21 | snapshot creation while scaling up RAM and CPU
| 1-Login through UI
2-click on upgrade SO
3-click create snapshot
4- Required Resources on host available | snapshot creation should fail | P2 | Functional | Y |
22 | snapshot creation while scaling up RAM and CPU
| 1-login through UI
2-click on upgrade SO
3-Click create snapshot
3-Required Resources not available on host
4-Resource available in same cluster | snapshot creation should fail | P2 | Functional | Y |
| Guest OS Support | | | | | |
23 | Guest OS does not support scaling up
| 1-Login through UI
2-click on upgrade SO
3-click create snapshot
4- Required Resources on host available | Should through a not supported exception
| | Functional | Y |
| Migration Fails(power off /service network stop , Destination host)
| | | | | |
25 | Scaling up CPU
| 1-in case no resources are available on current host, live migration to next host
2-issue Network down command . | 1-CS should try N times
2-If unsuccessful throw exception
| P1 | Functional | Y
|
| scaling up CPU | 1-in case no resources are available on current host, live migration to next host
2-Power off the destination host. | 1-CS should try N times
2-If unsuccessful throw exception | | | |
26 | scaling up RAM | 1-in case no resources are available on current host, live migration to next host
2-Power off the destination host. | 1-CS should try N times
2-If unsuccessful throw exception | P1 | Functional | N |
| scaling up RAM | 1-in case no resources are available on current host, live migration to next host
2-Power off the destination host. | 1-CS should try N times
2-If unsuccessful throw exception | | | |
27 | scaling up CPU and RAM
| 1-in case no resources are available on current host, live migration to next host
2-issue Network down command on destination host. | 1-CS should try N times
2-If unsuccessful throw exception | P1 | Functional | Y
|
| scaling up CPU and RAM | 1-in case no resources are available on current host, live migration to next host
2-issue Network down command on destination host. | 1-CS should try N times
2-If unsuccessful throw exception | | | |
| Scale Down | | | | | |
28 | Scale down CPU and Memory | 1- Upgrade vm with CO(=Compute offering) have less RAM and CPU than current CO
| should get a message "scale down not supported"
| P1 | | |
| UPGRADE | | | | | |
29 | upgrade path
| Pre upgrade Steps
1-Deploy some vms
2-Create some snapshots
3-create some compute offerings
FOLLOW UPGRADE STEPS DEFINE IN RELEASE DOC
Post upgrade steps
4-upgrade existing vms with compute offering (before upgrade)
5-Deploy a vm and Create new compute offering
6-upgrade existing vms with compute offering (created after upgrade)
7-Upgrade new vm using olde compute offering
8-upgrade new vm using new compute offering
(REPEAT FOR EACH SSVM,CPVM,VR,RVR)
9-upgeade ssvm with old offering
10-upgrade ssvm with new compute offering
| 1-upgrade should go properly
2-step 4 should fail
3-step 5 should be successful
4-step 6 should fail
5-step 7 should be successful
6-step 8 should be successful
7-step 9 should be successful
8-step 10 should be successful
| P1 | Functional | |
|
| | | | | |
31 |
|
|
| | | |
| Other | | | | | |
| Change SO of a stop VM
| 1-Stop vm
2-change SO
| step 2 should be successful
| | | |
| Restore VM
| 1- Scale up CPU/RAM
2-destroy vm
3-restore VM
| 1-Restore VM should boot using last used service offering by vm.
| | | |
| Dashboard | | | | | |
| scale up cpu /RAM
| 1-Change CO of a running VM
| Dashboard should display new value of CPU and RAM according to CO values.
| | | |
| Usage Event | | Waiting for FS update | | | |
