You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Test Case ID

Test Case Name

Steps

Expected Results

Priority
(P0 | P1 | P2)

Test Case Type
(Sanity/Upgrade/Performance/ Functional)

Automatable(Y/N)


CL01

Global configuration  check

1-Login Through UI
2-Click on "Global Settings"
3-Search for "vmware.percluster.host.max"

1-Global settings whould not have a attribute "vmware.percluster.host.max " .

 

 

 

 

CL02

DB check
  "hypervisor_capabilities" table

1-Login to DB
2- do following
 a- use cloud
 b-select * from hypervisor_capabilities;

1-Column "max_host_per_cluster
2- For vmware value should be "X"
3-For other hyperviser  should be NULL

 

 

 

 

CL03

upgrade path

1- upgrade from 4.0 to 4.1
 

1-Should successfully get upgrade
2- go to previous step

 

 

 

 

CL04

Addition of a cluster having number of host <="max_host_per_cluster"

1-Create a VMware cluster with size<="max_host_per_cluster". 
2-Add cluster to CS

1-CS should   allow addition of cluster  .

P0

 

 

 

CL06

Addition of  a cluster having number of host >"max_host_per_cluster"

1-Create a VMware cluster with size>"max_host_per_cluster". 
2-Add cluster to CS

1-CS should not  allow addition of cluster.

P0

 

 

 

CL07

Addition  of host  to a VMware cluster already in CS with size=max_host_per_cluster 

1-Add a cluster to CS having number of host equal to max_host_per_cluster
2-add one more host to same cluster.

1-CS should allow addition of cluster
2-CS should not allow addition of host 

P0

 

 

 

CL08

DataBase change effect

1-Login to DB
2- Change max_host_per_cluster to 5
3-Add a VMware cluster having cluster size 5 to CS
4-Change max_host_per_cluster to 3

1-Already added cluster should  work as expected
2-should not allow addition of host in existing cluster(which is having cluster size > =3) anymore.

P0

 

 

 

  • No labels