DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Hypervisor : VMwareAbbreviation |
|
|
|
|
| |
Test Case ID | Test Case Name | Steps | Expected Results | Priority | Test Case Type |
|---|
...
Automatable(Y/N) |
|---|
...
1 | UI and API |
| 1-Upgrade button should be present. | P0 | Functional |
|
| Y | |||
|
| User VM CPU/ RAM scale up |
|
|
|
|
|
|
| ||
2 | Scaling up CPU | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional |
|
| Y |
| ||
3 | Scaling up CPU | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional |
| Y | ||||
4 | Scaling up CPU | 1-Select a running user vm | 1-SO upgrade should fail. | P0 | Functional |
|
| Y |
| ||
5 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should be successful | P0 | Functional |
|
| Y | |||
6 | Scaling up RAM | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional |
|
| Y | |||
7 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional | Y |
| Y |
| ||
8 | 8 | Scaling up CPU and RAM | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional |
| Y | |||
9 | Scaling up CPU and RAM | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional |
|
| Y | |||
10 | Scaling up CPU and RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional |
|
| Y | |||
| System VM CPU/RAM scale up( Need to repeat for SSVM,CPVM,VR) |
|
|
|
|
|
|
|
| ||
11 | Scaling up CPU | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional |
| Y |
| |||
12 | Scaling up CPU | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional |
|
| Y | |||
13 | Scaling up CPU | 1-Select a running system vm | 1-SO upgrade should fail. | P2 | Functional |
|
| Y | |||
14 | Scaling up RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional |
| Y | ||||
15 | Scaling up RAM | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional |
|
| Y | |||
16 | Scaling up RAM | 1-Select a running system vm | 1-SO upgrade should fail. | P2 | Functional |
|
| Y | |||
17 | Scaling up CPU and RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional |
|
| Y |
| ||
18 | Scaling up CPU and RAM | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional |
| Y | ||||
19 | Scaling up CPU and RAM | 1-Select a running system vm | 1-SO upgrade should fail. | P2 | Functional |
|
| Y | |||
| Restart/power off VM during operation |
|
|
|
|
|
|
|
| ||
20 | Restart VM while scaling UP CPU | 1-Select a running vm | 1-DB should get updated with new compute offering | P0 | Functional |
| Y | ||||
21 | Restart VM while scaling UP CPU | 1-Select a running vm | 1-VM should live migrate | P0 | Functional |
|
| Y |
| ||
22 | Restart VM while scaling UP CPU | 1-Select a running vm | 1-SO upgrade should fail. | P2 | Functional |
|
| Y | |||
23 | Restart VM while scaling UP RAM | 1-Select a running vm | 1-DB should get updated with new compute offering | P0 | Functional |
|
| Y | |||
24 | Restart VM while scaling UP RAM | -Select a running vm | 1-VM should live mirgate | P0 | Functional |
| Y | ||||
25 | Restart VM while scaling UP RAM | -Select a running vm | 1-SO upgrade should fail. | P2 | Functional |
|
| Y | |||
26 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-DB should get updated with new compute offering | P0 | Functional |
|
| Y | |||
27 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-Vm should live migrate | P0 | Functional |
|
| Y |
| Y | |
28 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-SO upgrade should fail. | P2 | Functional |
| Y | ||||
| Restart system vms during operation( Need to repeat for SSVM,CPVM,VR ) |
|
| |
|
|
|
|
| ||
29 | Restart VM while scaling UP CPU | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional |
|
| Y | |||
30 | Restart VM while scaling UP CPU | 1-Select a running system vm | 1-VM should migrate | P1 | Functional |
|
| Y | |||
31 | Restart VM while scaling UP CPU | 1-Select a running system vm | 1-SO upgrade should fail | P2 | Functional |
| Y |
| |||
33 | Restart VM while scaling UP RAM | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional |
|
| Y | |||
34 | Restart VM while scaling UP RAM | 1-Select a running system vm | 1-VM should migrate | P1 | Functional |
|
| Y | |||
35 | Restart VM while scaling UP RAM | 1-Select a running system vm | 1-SO upgrade should fail | P2 | Functional |
| Y | ||||
36 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional |
|
| Y | |||
37 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | 1-VM should migrate | P1 | Functional |
|
| Y | |||
38 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | 1- SO upgrade should fail | P2 | Functional |
|
| Y | |||
|
| Snapshot creation while scaling up CPU/RAM |
|
|
|
|
|
|
| ||
39 | snapshot creation while scaling up RAM | 1-Select a running system vm. | snapshot creation should fail | P2 | Functional |
|
| Y | |||
40 | snapshot creation while scaling up CPU | 1-Select a running system vm. | snapshot creation should fail | P2 | Functional |
|
| Y |
| ||
41 | snapshot creation while scaling up RAM and CPU | 1-Select a running system vm. | snapshot creation should fail | P2 | Functional |
| Y | ||||
| Guest OS Support |
|
|
|
|
|
|
| |||
42 | Guest OS does not support scaling up | 1-Select a running user VM | Should throw "not supported exception" | P3 | Functional |
|
| Y | |||
| CS behavior when migration fails while scaling up CPU/RAM(power off /service network stop , Destination host) |
|
|
|
|
|
|
| |||
43 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
| Y | ||||
44 | scaling up CPU | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
45 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
46 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-CS should try N times | P2 | Functional |
|
| y |
| y | |
46 | scaling up RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
| Y | ||||
47 | scaling up RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
48 | scaling up RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
50 | Scaling up RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P2 | Functional |
|
| Y | |||
51 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
| Y |
| |||
52 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
53 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P1 | Functional |
|
| Y | |||
54 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-CS should try N times | P2 | Functional |
| Y |
|
|
|
|
|
|
|
|
|
| ||||||
55 | scaling up RAM(at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) | P1 | Functional |
| | Y | |||
56 | Scaling up CPU (at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) | P1 | Functional |
|
| Y |
| ||
57 | scaling up CPU and RAM (at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) | P! | Functional |
| Y | ||||
| Scale Down |
|
|
|
|
|
|
| |||
58 | 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 | Functional |
|
| Y | |||
| UPGRADE |
|
|
|
|
|
|
| |||
59 | upgrade path | Pre upgrade Steps | 1-upgrade should go properly | P1 | Upgrade |
| | N | |||
|
| Other |
|
|
|
|
|
|
|
| |
60 | Change SO of a stop VM | 1-Stop vm | step 2 should be successful |
| Functional |
|
| Y | |||
61 | Restore VM | 1- Scale up CPU/RAM | 1-Restore VM should boot using last used service offering by vm. |
| Functional |
| Y | ||||
| Dashboard |
|
|
|
|
|
|
| |||
62 | scale up cpu /RAM | 1-Change CO of a running VM | Dashboard should display new value of CPU and RAM according to CO values. |
| Functional |
|
| N |
|
| |
|
|
|
|
|
|
|
|
| |||
63 | Usage Event |
| Waiting for FS update |
|
|
| |||||
|
|
| Race condition |
|
|
|
|
|
|
| |
64 | update to many vms on same host | Update too many(5-10) vms on same host | vm should get updated without error-exception |
| Functional |
| | Y | |||
65 | Manage-Unmanage cluster | 1-update vm (cpu and RAM) | 1-step 2 should not have any effect on step 1 |
| Functional |
| | Y | |||
66 | Disable-Enable cluster/pod/zone | 1-Updtade vm | 1-step 2 should not have any effect on step 1 |
| Functional |
| | Y |
| ||
67 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional |
|
| Y | |||
| Cluster have capacity but host doesn't |
|
|
|
|
|
|
|
| ||
68 | cluster.cpu.allocated.capacity.disablethreshold | set cluster.cpu.allocated.capacity.disablethreshold to some value] | should not be allowed to scale up because cluster will not have resources after threshold value |
| Functional |
| Y | ||||
69 | cluster.memory.allocated.capacity.disablethreshold | set cluster.cpu.allocated.capacity.disablethreshold to some value | scale up should not not be allowed because cluster will not have resources after threshold value |
| Functional |
|
| Y | |||
70 | force connect host | update vm then force reconnect/put host in maintenance mode | update vm should not get affected because of reconnect and mainenance mode. |
| Function |
| | Y |