Note:    1)Need to test this in both Advanced and Basic Zone as well as on all hypervisors(Xen,Vmware,KVM versions will be updated).
            2)Setup Assumes the api port 8096 is opened.

TestID

Test Case

Steps To Be Performed to Test

Verification Steps

Priority

Reviewed By

1)

Create Service Offering

Create a Service offering with IsVolatile as true.

The Service offering Should be Successfully created.

P1

2)

Create a VM  with VM reset.

Create a VM by Selecting the Service offering with the IsVolatile set to true

VM Should be Successfully Created.Note the UUID of the root disk

P1

3)

Create VM without VM Reset.

Create a VM by Selecting the Service offering with the IsVolatile set to false

VM Should be Successfully Created.Note the UUID of the root disk

P1

4)

Reboot the VM with Vmreset enabled.

Reboot the VM created in using the Service offering with the IsVolatile set to true.

The VM Should be booted with new RootDisk the UUID Should be different from the previous but the IPAddress and other memory alloctions should not change.

P1

5)

Reboot the VM with Vmreset not enabled.

Reboot the VM created in using the Service offering with the IsVolatile set to false.

The VM Should be booted with same RootDisk the UUID,  IPAddress and other memory alloctions should not change.

P1

6)

Add Multiple Templates/ISO's.

Add Templates/and ISO's of multiple OS(eg:Centos 6.2,5.5,Rhel6.2,6.3,5.7)

The Templates Should be added Successfully and make noteof UUID's of all templates

P1

7)

Create Multiple Vm's with different OS ISO's and Tempaltes

Create Multiple Vm's with different OS ISO's and Tempaltes using UI as well as API's

The Vm's Should be Successfully created.Note the Root Disk UUID's of the VM's Created.

P1

8)

Fire the restoreVirtualMachine API.

Fire the restoreVirtualMachine API using the UUID of the template or ISO to which you want to change the base image .

The VM Should be recreated with a new root disk having the new Base Image and UUID but the Ipaddress and other memory allocations should be same

P1

9)

Reboot a VM with Recurring Snapshot enabled.

Create a VM using the Service offering IsVolatile enabled and apply a recurring snapshot rule on the  Volume.
After a couple of snapshots are taken reboot the VM.

New root disk should be formed and the recurring snapshot rule should be deleted and no error messages should be seen during the scheduled time .

P2

1)

Perform the Upgrade from 4.0 to 4.1.

Perform the Upgrade from 4.0 to 4.1 having multiple ISO'sTemplates and
VM's

The Upgrade Should  be Successful.

P1.

2)

Create Service Offering

Create a Service offering with IsVolatile as true on the Upgraded setup

The Service offering Should be Successfully created.

P1

3)

Create a VM  with VM reset.

Create a VM by Selecting the Service offering with the IsVolatile set to true

VM Should be Successfully Created.Note the UUID of the root disk

P1

4)

Reboot the VM with Vmreset enabled.

Reboot the VM created in using the Service offering with the IsVolatile set
to true.

The VM Should be booted with new RootDisk the UUID Should be
different from the previous but the IPAddress and other memory
alloctions should not change.

P1

5)

Reboot the Vm's Created before the Upgrade.

Reboot the Vm's Created before the Upgrade.

The VM Should be booted with same RootDisk the UUID,  IPAddress
and other memory alloctions should not change.

P1

6)

Fire the restoreVirtualMachine API.

Fire the restoreVirtualMachine API using the UUID of the template or ISO
to which you want change the base image .(fire it on both the Vm's
Created before and after upgrade.)

The VM Should be recreated with a new root disk having the new Base
Image and UUID but the Ipaddress and other memory allocations
should be same

P1

7)

Reboot a VM with Recurring Snapshot enabled.

Create a VM with Root disk and apply a recurring snapshot rule on the root disk.
Upgrade the VM and then fire the api for the restoreVirtualMachine.

New root disk should be formed and the recurring snapshot rule should be deleted and no error messages should be seen during the scheduled time.

P2

1)

Fire the restoreVirtualMachine API with Invalid UUID

Fire the restoreVirtualMachine API with Invalid UUID

Proper Error message Should be poped up.

P2