Test Case IdTest Case NameStepsExpected ResultStatus(pass/fail)CommentsSecond Cycle execution statusComments
1create  (Dynamic )compute
offering
Create CO through API with following parameters
Static CO
1-provide values for cpu,# of cpu cores, memory.
Dynamic CO
2-provide no value for cpu, # of CPU Cores,memory and create SO
3-provide no value for cpu and create so
4-provide no vlaue for #cpu cores and create so
5-provide no value for mem and create so
1-CO creation should be allowed in step 1 and 2
2-CO creation should be failed in other steps
pass Pass 
2Deploy vm from admin accountIn deploy vm API salect following and deploy vm
(steps #  refer steps 1st test case)
static CO
1-Deploy vm with co created in step 1
1a-provide value for cpu,# of cpu cores and mem.
Dynamic CO
2-Deploy vm with co created in step 2
2a-provide value for all params(cpu,#cpu,mem)
2b-provide value for any of them
1-deploy vm should be successful in cases 1 and 2a
2-deploy vm should fail in cases ,1a,2b.
pass passhttp://bugs-ccp.citrix.com/browse/CS-18848
3Deploy vm from user accountIn deploy vm API salect following and deploy vm
(steps #  refer steps 1st test case)
Static CO
1-Deploy vm with co created in step 1
1a-provide value for cpu,# of cpu cores and mem.
Dynamic CO
2-Deploy vm with co created in step 2
2a-provide value for all params(cpu,#cpu,mem)
2b-provide value for any of them
1-deploy vm should be successful in cases 1 and 2a
2-deploy vm should fail in cases ,1a,2b.
Pass pass 
4check vm statistics

1-deploy a vm using dynamic service offering

2-check vm statistics

1-IN vm statistics cpu and ram should be based on dynamic coFailhttps://issues.apache.org/jira/browse/CLOUDSTACK-5472  
5Change CO of stop VM
(repeat it for user and admin)
Stop a vm and change to following CO using API
(steps #  refer steps in 1st test case)
1-change to  co created in step 1
1a-provide value for cpu,# of cpu cores and mem.
2-change co created in step 2
2a-provide value for all params(cpu,#cpu,mem)
2b-provide value for any of them
3-Change CO for vms
3a-from static to daynamic
3b-from dynamic to static
3c-from dynamic to dynamic b/w different
dynamic co
3d-from dynamic to dynamic b/w same dynamic co
1-Change SO should be successful in c
 ase of 1,2a,All 3.
2-Change CO chould be fail  in case
1a,2b

Pass
UI changes required
Raised a UI bug(problem b/w same SO)
pass 
6Change CO of running VM
(repeat it for user and admin)
Stop a vm and change to following CO using API
(steps #  refer steps in 1st test case, all the value should be
larger than current CO  )
1-change to  co created in step 1
1a-provide value for cpu,# of cpu cores and mem.
2-change co created in step 2
2a-provide value for all params(cpu,#cpu,mem)
2b-provide value for any of them
3-Change CO for vms
3a-from static to daynamic
3b-from dynamic to static
3c-from dynamic to dynamic b/w different
dynamic co
3d-from dynamic to dynamic b/w same dynamic co
1-Change SO should be successful in c
 ase of 1,2a,ALL 3.
2-Change CO chould be fail  in case
1a,2b.
pass pass 
7Gloabal Min and Global Max
(repeat it for user and admin)
1-set glabal min and global max.
2-create a custom co
3-provide values more than the global max while deploying vm, changing co.
4-provide values less than the global min while deploying vm,changing co.
5-provide any values b/w Glaobal min and Global min while deploying vm,changing co.
1-step 2,3 and 4 should fail.
2-step 5 should be successful.
N/Ahttps://issues.apache.org/jira/browse/CLOUDSTACK-5565N/A 
8max.account.cpus
max.account.memory
max.account.vcpus
(repeate it for user and admin)
1-deploy vm and change co should honor these
parameters.
1-Should be successfulPass   
9cluster.cpu.allocated.capacity.
Disablethreshold
cluster.mem.allocated.capacity.disablethreshold
1-deploy vm and change co should honor these
parameters.
1-Should be successfulPass   
10usage
(repeat it for user and admin)

1-for vm createed using dynamic compute offering
there should be an entry in usage_detail table.
2-usage_vm_instance table should get updated with  details in usage_detail and usage_vm_instance table should have new fields for cpu,ram and #cpu.

3-perform following operation

3a-stop-start vms

3b-reboot vm

3c-destroy vm

3d-change CO of running vm

3f-change CO of stopped vm

 

1-dynamic offering should  get updated in
usage_details table .
2-Usage server should update usage_vm
_instance table  successfully

3-In all the cases proper usage events should be updated in usage server.

fail

https://issues.apache.org/jira/browse/CLOUDSTACK-5515

https://issues.apache.org/jira/browse/CLOUDSTACK-5742

Passhttp://bugs-ccp.citrix.com/browse/CS-19028
11upgrade testingpre upgrad steps
-Create some CO and vm.
Post upgrade steps
1-Create dynamic CO deploy vms using dynamic CO
2-perform following for vms created after and before upgrade
2a-Change CO of stop vm from dynamic to static CO and  viceversa
2b-Change SO of running vm from dynamic to static CO and viceversa
3-check usage records are getting generated  or not
1-All steps should be successful.

pass

Blocked on usage

https://issues.apache.org/jira/browse/CLOUDSTACK-5539Pass 
12Affinity Group

1-create a Affinity group

2-create a dynamic compute offering

3-Deploy a vm

4-Try to deploy another vm

1-deployment in step-3 should be successful

2-step 4 should fail since there is only one host in a cluster.

 

Pass   
13Live migration

1-deploy a vm with custom compute offering .

2-try to live migrate it to othe host in cluster

1-VM should migrate successfully- failhttp://bugs-ccp.citrix.com/browse/CS-19093
14UI changesFor tracking UI issues.   fail

http://bugs-ccp.citrix.com/browse/CS-19032

http://bugs-ccp.citrix.com/browse/CS-18854

  • No labels