...
SNO | Testcase Name | Procedure | Expected Results | Test Case Type( Sanity | Functional |Negative) | is Automatable | Priority | Pass/Fail | Comments | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Verify_Host_transition_states | 1. Add each Host to each cluster and make sure each host managed by each MGMT server | 1. Check the Host state changed | SANITY, | N | P1 |
|
| ||||||
2 | Only_One MS_UP | 1.Make sure each host is managed by each management server | a)Able to access the MS UI from MS3 | SANITY, | Y | P2 |
|
| ||||||
3 | All_MGMTServices_UP_at_sameTime | 1.Make sure each host is managed by MGMT server | Hosts should get re-distributed to all the 3 management servers. deployVM should be successful without | FUNCTIONAL | Y | P2 |
|
| ||||||
4 | restart_ALL_MGMT services's | 1.Make sure each host is managed by each MGMT server | All the MGMT server should up | FUNCTIONAL/ |
| P2 |
|
| ||||||
5 | Change_SystemDate_ON_1MGMT Server | 1.Make sure each host is managed by each MGMT Server | When one of the MS date is not synched | FUNCTIONAL/ |
| P3 |
|
| ||||||
6 | Perform_task_From_non-managed_MS | 1.host 1 is managed by MS1 | 1. task should be forward to managed MS(MS1) from MS2 and executed at MS1 and response should be received back to task initiator(i.e MS2) | SANITY, | Y | P1 |
|
| ||||||
7 | Perform_Task_From_non-Managed MS_StopMS | 1.host 1 is managed by MS1 | Async Job shouldn't be in progress and it should be Done state. | FUNCTIONAL/ |
| P2 |
|
| ||||||
8 | verify_ForwardAgent_becomes DA | 1.Stop the MS1 | From MGMT2,Direct Agent Request transferred to MGMT2 from MGMT1 and Vm deployment should | SANITY, FUNCTIONAL | Y(Its possible to automate | P1 |
|
| ||||||
9 | verify ForwardAgent_functionality | 1.Stop the MS1 | 3.Request get forwarded to MGMT2 from MGMT3 and Vm deployment should successful on MS2. | SANITY, FUNCTIONAL | Y | P1 |
|
| ||||||
10 | Host_Force_reconnect_From_non-managed MS | Find the management server that owns | We should see the request | FUNCTIONAL |
| P1 |
|
| ||||||
11 | Host-maintenance_Mode_Mgmg_status | 1.Select the Host from any MGMT server(says MS1) 2.Put the Host into maintenance mode | 2.Host should be maintenance mode | SANITY, FUNCTIONAL |
| P2 |
|
| ||||||
12 | Cancel_MaintenanceMode | 1.Select the Host from any MGMT server(say MS2) 2.Put the Host into maintenance mode | 3.MGMT_ID should be Null | SANITY, FUNCTIONAL |
| P1 |
|
| ||||||
13 | Take the Host out of maintenance Mode | Find the management server that owns this host. | We should see the requests for both | SANITY, FUNCTIONAL |
| P1 |
|
| ||||||
14 | HostMaintenance_Join_MS | 1.Select the Host from any MGMT server | when Host is in maintenance | FUNCTIONAL |
| P2 |
|
| ||||||
15 | Cancel_Maintenance_Join_MS | 1.Select the Host from any MGMT server(Say MS1) | 2..MGMT_ID should be Null | SANITY, FUNCTIONAL | Y | P2 |
|
| ||||||
16 | StopMS1_Cancel_Maintenance Mode_fromMS2 | 1.Select the Host from any MGMT server(eg:MS1) | 3.MGMT_ID should be Null | SANITY, FUNCTIONAL | Y | P2 |
|
| ||||||
17 | AsyncJobState_StopMS_while_Job(Maintenance)_inProgress | 1.Select the Host owned by MGMT server(eg: | Async job should not be | SANITY, FUNCTIONAL | Y | P2 |
|
| ||||||
18 | DeleteHost_from_other_MS | Find the management server that owns this host. | We should see the requests for | FUNCTIONAL | Y | P1 |
|
| ||||||
19 |
|
|
| FUNCTIONAL | AsyncJobState_StopMS_while_Job(Snapshots)_inProgress | From the management server which is NOT the | Async job should get marked as | FUNCTIONAL | Y | P2 |
|
| ||
20 |
|
| AgentLB_HostState_UP_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each | MS1 gives away 2nd cluster & | FUNCTIONAL |
| P1 |
|
| ||||
21 |
|
|
|
|
| AgentLB_HostState_Down_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each | No agent load balancing will | FUNCTIONAL |
| P2 |
|
| |
22 |
|
|
|
|
| AgentLB_ThresHold_lessThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each | No agent load balancing will trigger | SANITY, FUNCTIONAL |
| P1 |
|
| |
23 |
|
|
|
|
| AgentLB_ThresHold_moreThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each | Agent load balancing will | SANITY, FUNCTIONAL |
| P1 |
|
| |
24 |
|
|
|
|
|
|
|
| ||||||
25 |
|
|
|
|
|
|
|
| ||||||
|
|
|
|
|
|
|
|
| ||||||
|
|
|
|
|
|
|
|
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AgentLB_ThresHold_moreThan_Non_default_ value | 1. zone> pod1> cluster1 cluster2 cluster3 | Agent load balancing will | FUNCTIONAL |
| P2 |
|
| |||||||
25 | Direct agent-loads |
26 | AgentLB_sourceMS_down_during_Re-balancing | 1. In multi clustered Env, make sure all hosts | All hosts already transferred to MS2 should get new MGMT server ID. | FUNCTIONAL |
| P2 |
|
|
27 | AgentLB_DestinationMS_Down_during_Rebalancing | 1. In multi clustered Env, make sure all hosts | If M2 dies, all re balancing should be stopped as it's running on M2. All hosts already transfered to M2 should be marked as Disconnected. | SANITY, FUNCTIONAL |
| P1 |
|
|
28 | dbServer_ UsageServer on different machines | 1. configure cluster management setup and Make sure database and usage on separate machine | In all the cases usage statistics should be collected and details should be accurate | SANITY, FUNCTIONAL |
| P1 |
|
|
29 | dbServer_ UsageServer on _Same_Machines | 1. configure cluster management setup and Make | In all the cases usage statistics should be collected and details should be accurate | SANITY, FUNCTIONAL |
| P1 |
|
|
30 | Ping Timeout | 1.make sure all the MS's are synch | once ping command timeouts,The corresponding MS will be disconnect state and host on the current MS(M2) will get the another management ID(MS3 ID) | Negative |
|
|
|
|
...
...
...
...
...
...
...
31 | Upgrade test(2.2.14 to Bonita and 3.0 to Bonita) | 1.prepare the cluster management setup before upgrade 2. perform basic operations(vm life-cycle,snapshots) | Upgrade should be successful, | SANITY, FUNCTIONAL |
| P1 |
...
...
...
...
...
...
...
|
|