THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Test Case Id | Test Case Name | Steps | Expected Result | Status(pass/fail) | Comments | Second Cycle execution status | Comments |
|---|---|---|---|---|---|---|---|
| 1 | create (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 | ||
| 2 | Deploy vm from admin account | In 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 | ||
| 3 | Deploy vm from user account | In 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 | ||
| 4 | check 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 co | Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-5472 | ||
| 5 | Change 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 | |
| 6 | Change 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 | ||
| 7 | Gloabal 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/A | N/A | ||
| 8 | max.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 successful | Pass | |||
| 9 | cluster.cpu.allocated.capacity. Disablethreshold cluster.mem.allocated.capacity.disablethreshold | 1-deploy vm and change co should honor these parameters. | 1-Should be successful | Pass | |||
| 10 | usage (repeat it for user and admin) | 1-for vm createed using dynamic compute offering 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 3-In all the cases proper usage events should be updated in usage server. | fail | Pass | h | |
| 11 | upgrade testing | pre 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 | Pass | ||
| 12 | Affinity 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 | |||
| 13 | Live 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 | - | fail | http://bugs-ccp.citrix.com/browse/CS-19093 | |
| 14 | UI changes | For tracking UI issues. | fail |
Overview
Content Tools
Apps