DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Page History
| Table of Contents |
|---|
Browser-based Template / Volume upload Test Plan @ BrowserBasesvolume_or_template_upload_Test_Plan_3.xlsx
Test cases
| Ref | Test Step | Variants | Verify | Can Automate (Yes/No) |
Hypervisor - Vmware,KVM,XenServer,HyperV , Storage - NFS,iSCSI(Vmware) , SMB(HyperV) Guest OS - Windows 8 , Win 2012 , RHEL 6.5 , Storage- Local, Shared , Account - Root Admin , User , Domain Admin | ||||
| Test Path 1: Browser Based Volume Life Cycle | ||||
| Deploy | ||||
| D1 | Deploy Zone1(shared storage) | |||
| D2 | Deploy Zone 2 with Shared Storage added to the deployment (Zone wide primary , Cluster wide Primary) | |||
| D3 | Setup the domain name - Reference 1. Procedure to Replace realhostip.com with Your Own Domain Name 2. Implementation details and troubleshooting - uploading custom domain certificate instead of using realhostip.com | |||
| D4 | Install and Configure Usage Server | |||
| D5 | Add multilple secondary Storages | |||
| Setup | ||||
| S1 | Create Domain Admin DA1 , User Account UA1 , Account added to the Project | |||
| S2 | Create Custom Disk Offering with Local Storage - LDO1 | |||
| S3 | Create Custom Disk Offering with Shared Storage - SDO1 | |||
| S4 | Create Disk Offering with Shared Storage - SDO2 with storage tags | |||
| S5 | Create Isolated Guest Network -GN1 | |||
| S6 | Register Template Windows 8, Windows 2012, RHEL 6.5 | |||
| S7 | Deploy VM's with no additional disk using the templates created S5 on Zone1 created in D1 | |||
| S8 | Deploy VM's with additional disk using the templates created S5 on Zone2 created in D2 | |||
| Tests | ||||
| T1 | Browse volume and upload 1GB volume using the offering created in S2 as UA1 | Done | Upload and download of volume to be successful , List Volumes and verify the Volume details , Verify the Events , Notifications generated in the UI flow , Verify the Storage where this volume got downloaded, Verify the state of the volume to transit from NOT_UPLOADED => UPLOAD_IN_PROGRESS => UPLOADED, Verify DB for the download URL entry | Yes |
| T2 | Browse volume and upload 1GB volume using the offering created in S2 as UA1 - NFS location mounted on dsektop | Done | ||
| T3 | Attach the volume to a VM created in S7 | Done | Verify the state of the volume . Verify | Yes |
| T4 | Write the data to the newly added volume | Verify the state of the volume | Yes | |
| T5 | Add multiple upload volumes using custom Disk offering | Done | Verify the state of the volume | Yes |
| T6 | Attach multiple uploaded volumes to the instance | Done | Verify the state of the volume | Yes |
| T7 | Stop and start Virtual machine after attaching the volume | Done | Verify the state of the volume | Yes |
| T8 | Detach the volume | Done | Verify the state of the volume | Yes |
| T9 | Attach the detached volume to a new instance | Done | Verify the state and contents of the disk | Yes |
| T10 | Reset VM when it has the uploaded data volume attached | Done | Verify the uploaded volume state during reset and after reset VM | Yes |
| T11 | Resize the uploaded detached volume | Done | Verify the volume size in the storage , Resource limits | Yes |
| T12 | Attach the resized detached volume to a new instance | Done | Verify the volume size in the storage , Resource limits | Yes |
| T13 | Resize the volume when its attached to the instance | Done | Verify the volume size in the storage , Resource limits | Yes |
| T14 | Resize the volume after upload is completed and before attaching to any instance | Done | Verify the volume size in the storage , Resource limits | Yes |
| T15 | Upload the volume with md5 sum | Done | Verify the md5sum after its downloaded to Secondary storage | Yes |
| T16 | Verify the Download volume POST URL expiry | Verify the expire URL and redown before and after expiry time. | Yes | |
| T17 | Take the volume backup snapshot | Verify from backend (Hypervisor) and from secondary storage | Yes | |
| T18 | Schedule recurring snapshot on uploaded volume | Verify from backend (Hypervisor) and from secondary storage | Yes | |
| T19 | Download the uploaded volume | Done | Verify that uploaded volume downloadble URL and its expiry time validity | Yes |
| T20 | Create the template from the snapshots created on uploaded volume | Done | Ensure the existent behavior and verify that template creation works fine. Verify this template availability in the secondary storage | Yes |
| T21 | Create the volumes from the snapshots created on uploaded volume | Done | Ensure the existent behavior and verify that volume creation works fine. Verify this template availability in the secondary storage | Yes |
| T22 | Attach these volumes to the instances | Verify the availability of this volume under primary storage | Yes | |
| T23 | Recover the destroyed VM which has uploaded data volume attached | Done | Ensure that DATA volumes remain attached to the instance and ability to write into the volumes after recovering the VM | Yes |
| T24 | Change the domain name and try Uploading the volume | Verify the Upload Volume parameters to generate new values | Yes | |
| T25 | Upload the volume with POST URL as HTTP type using curl | It should allow only HTTPS | Yes | |
| T26 | Delete the Uploaded volume before attaching to the instance | Done | Verify that its cleaned from secondary storage | Yes |
| T27 | Delete the detached upload volume | Done | Verify that its cleaned from Primary storage | Yes |
| T28 | Assign the VM which has these upload volumes attached to a new account | Verify that DATA volumes ownership change and ability to write | Yes | |
| T29 | VMSnapshot with Disk and Memory of the VM with upload volume | Currently its not allowed to create VMSnapshot when it has volumes attached. Verify this | Yes | |
| T30 | VMSnapshot with Disk of the VM with upload volume | Currently its not allowed to create VMSnapshot when it has volumes attached. Verify this | Yes | |
| T31 | Revert VM Snapshot | Currently its not allowed to create VMSnapshot when it has volumes attached. Verify this | Yes | |
| T32 | Reboot VM when it has upload volume attached | Done | Verify that reboot works fine and ability to write into DATA volume | Yes |
| T33 | Delete the VM which has upload volume attached | Verify that DATA volumes gets into detached state after deleting the VM | Yes | |
| T34 | Upload Volume when there are multiple secondary storages available in a single zone | Verify the correct URL generation during upload | ||
| T35 | Upload Template when there are multiple secondary storages available in a single zone | Verify the correct URL generation during upload | ||
| T36 | Attach upload volumes to a VM which has VM Snapshots created | Currently its not allowed to add volumes to a VM which has VMSnapshot. Verify this | ||
| T37 | Detach the volumes and try creating VM Snapshots with Disk and Memory | Currently its not allowed to add volumes to a VM which has VMSnapshot. Verify this | ||
| T38 | Detach the volumes and try creating VM Snapshots with Disk | Verify that it allows to create VM Snapshot after detaching the upload volumes | ||
| T39 | Attach upload volumes to a VM after removing the VM Snapshots created on it | Verify that it allows to attach volumes after removing the VM Snapshots | ||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the Service Offering | |||
| Test Path 2: Browser Based Template Life Cycle | ||||
| Tests | Yes | |||
| T1 | Browse and upload the template | Validate the States of the template , | Yes | |
| T2 | Deploy instance using uploaded template with root volume only | Verify that deployment is successful | Yes | |
| T3 | Attach Volumes to this instance and write data on the newly attached volume | Verify the ability to add volumes to the VM which is created using upload template | Yes | |
| T4 | Deploy instance using uploaded template with additional data volumes | Verify the ability to add volumes to the VM which is created using upload template | Yes | |
| T5 | Create VM Snapshot of this instance with Disk only | Verify that VMSnapshot works fine | Yes | |
| T6 | Create VM Snapshot of this instance with Disk and memory | Verify that VMSnapshot works fine | Yes | |
| T7 | Revert VM Snapshot with Disk | Verify that Revert VMSnapshot works fine | Yes | |
| T8 | Revert VM Snapshot with Disk and Memory | Verify that Revert VMSnapshot works fine | Yes | |
| T9 | Create ROOT volume snapshot of the instane created using uploaded template | Verify the Disk Chain and Path only on Vmware | Yes | |
| T10 | Recover the instance deployed with Browser based template | Verify the Disk Chain and Path only on Vmware | Yes | |
| T12 | Reset the Instance with the Browser based Template | Verify the Disk Chain and Path only on Vmware | Yes | |
| T13 | Upload the template as Public and made it is available for other users to deployment | It should be available to all the users | Yes | |
| T14 | Copy the template across zones | Ensure that it is avilable in second zone secondary storage | Yes | |
| T15 | Reduce the default time till the template can be available in the primary storage and reinitiate the VM deployment after it Is removed from primary storage | Verify that templates gets copied to primary storage once it finds its not available | Yes | |
| T16 | Download the uploaded template | Verify that its able to download , Verify the DB entries for the URL expiry | Yes | |
| T17 | Upload Password enabled template and use it for deployment . | Verify that it generates the password correctly | Yes | |
| T18 | Delete the template | Verify that its deleted from secondary and primary storage , Its references in DB marked as removed | Yes | |
| T19 | Create Private templates and use them for deploying the VM | Verify that private templates are not available for others to use it for deployment. Verify that its copied to secondary storage | ||
| Cleanup | ||||
| C1 | Delete the account | All references of the account has to be deleted | ||
| C2 | Delete the service offerings | Verify that the service offerings created during this test are cleaned up with no issues | ||
| C3 | Delete the domain | All References of the domain has to be deleted | ||
| Test Path 3: Browser Based Volume Storage Migration | ||||
| Tests | ||||
| T1 | Cold Migrate the upload volume to another primary storage when VM is in stopped state | Verify that Volumes got migrated to another store. Verify the Disk Path on Vmware | Yes | |
| T2 | Stop and start the VM after migration | Verify VM got started post cold migration. And DISK volume remained in the migrated primary storage | Yes | |
| T3 | Migrate the detached upload volume to another storage | Verify that Volumes got migrated to another store. Verify the Disk Path on Vmware | Yes | |
| T4 | Attach the upload volume to an instance after volume migration | Verify that volume gets attached and veriy Path and Disk chain info | Yes | |
| T5 | Resize the uploaded volume post migration | Verify that Volumes got resized from the primary storage . Verify the storage limits | Yes | |
| T6 | Migrate the upload volume after downloading the uploadvolume | We had an issue with migration after download URL is generated | Migrate should work after download | Yes |
| T7 | Migrate the errored uploaded | Verify the error message | Yes | |
| T8 | Migrate the uploaded volume to a the same cluster and to an additional PS added to the cluster | Migrate should work . Check the Path | Yes | |
| T9 | Migrate the uploaded volume to a different cluster Primary storage | Migrate should work . Check the Path | Yes | |
| T10 | Migrate the uploaded volume to a different zonewide Primary storage | Migrate should work . Check the Path | Yes | |
| T11 | LiveMigrate the VM with volumes to another storage in the same cluster | Migrate should work . Check the Path | Yes | |
| T12 | LiveMigrate the VM with volumes to another storage in a different cluster | Migrate should work . Check the Path | Yes | |
| T13 | Live Migrate VM with upload volumes after deleting the VMSnapshots | Migrate should work after VMSnapshot deletion | Yes | |
| T14 | Stop and start the VM live after migration | Verify the disks are available to write the data | ||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 4: Storage Global Config Parameters Validation | ||||
| Tests | ||||
| T1 | Global configuration to limit the max upload size of template/volume - upload.post.max.size | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T2 | Hidden configuration to save sha1 PSK on the management server - upload.post.psk | Need verification steps?? Koushik to confirm this | ||
| T3 | Management server upload polling interval and polling timeout - upload.post.interval, upload.post.timeout | Verify time out errors when its not uploaded within the timelimit | ||
| T4 | storage.cleanup.enabled | |||
| T5 | storage.cleanup.interval | |||
| T6 | storage.max.volume.upload.size | Upload request need to get rejected | ||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 5: Browser based Volume , Template Resource Limits validation | ||||
| Tests | ||||
| T1 | Acccount Upload volume Limits | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T2 | Account Primary Storage limits while using Upload volume | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T3 | Account Upload templates limites | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T4 | Account Ssecondary storage limits while using Upload templates | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T5 | Domain Upload volume limits | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T6 | Domain Upload template limits | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T7 | Domain Primary storage limites while using upload volumes | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T8 | Domain secondary storage limits while using upload templates | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T9 | Global config validations for upload volumes | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | ||
| T10 | Global config validations for upload templates | Verify Resource Limits ( used vs limits ) and validate the error message when it crossed the defined limits | Yes | |
| Yes | ||||
| Cleanup | Yes | |||
| C1 | Delete the account | Yes | ||
| C2 | Delete the service offerings | Yes | ||
| Yes | ||||
| Test Path 6: Usage Validation for Browser Based Volumes and Templates | Yes | |||
| Tests | Yes | |||
| T1 | Verify the usage server validation for uploaded volumes | Yes | ||
| T2 | Verify the usage server validation for uploaded templates | Yes | ||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 7: Upgrade | ||||
| Deploy | Deploy | |||
| D1 | Upgrade from 4302 to 4.5.1 | |||
| D2 | Upgrade from 307G to 4.5.1 | |||
| Tests | ||||
| T1 | Schema comparison with fresh vs upgraded setup for the newly added Global config Parameters | 1) Global configuration to limit the max upload size of template/volume - upload.post.max.size 2) Hidden configuration to save sha1 PSK on the management server - upload.post.psk 3) Management server upload polling interval and polling timeout - upload.post.interval, upload.post.timeout 4) Time interval at which the GC or cleanup thread should run - upload.post.gc.interval | ||
| T2 | Browse and upload new volumes | Verify that it works | No | |
| T3 | Attach volumes created in T2 to the existing instances | Verify that it works | No | |
| T4 | Attach volumes created in T2 to the newly created instances post upgrade | Verify that it works | ||
| T5 | Browse and upload new templates | Verify that it works | ||
| T6 | Deploy VM using this new template | Verify that it works | ||
| T7 | Reset VM using this new template | Verify that it works | ||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | No | ||
| Test Path 8: Negative Testing | Will Rerun automation Post upgrade | |||
| Tests | Will Rerun automation Post upgrade | |||
| T1 | Reuse the Post URL (Volume)and use CURL to upload into Secondary storage | Will Rerun automation Post upgrade | ||
| T2 | Reuse the Post URL (Template)and use CURL to upload into Secondary storage | Will Rerun automation Post upgrade | ||
| T3 | Restart SSVM before it starts the upload using Post URL and get the Volume upload failure | ABANDONED: (TBD: Do we really need to distinguish ERROR and ABANDONED?) IS it Still Open? | Validate the state :UPLOAD_ERROR | Will Rerun automation Post upgrade |
| T4 | Attach the data volume when Upload is In progress | It should fail with right message | ||
| T5 | Attach the errored data volume | It should fail with right message | ||
| T6 | Restart SSVM before it starts the upload using Post URL and get the Volume upload failure | |||
| T7 | Restart MS and ensure upload wont start for Browser based templates | verify that download is not reinitiated for templates | ||
| T8 | Restart MS when upload of volumes Is InProgress and verify that download is not reinitiated | verify that download is not reinitiated for volumes | ||
| T9 | Delete the volumes when Upload is in Progress | It should fail with right message | ||
| T10 | Delete the templates when Upload is in Progress | It should fail with right message | ||
| T11 | Add Upload volume with defined Disk offering | It should fail with right message | ||
| T12 | Tamper the POST URL and try posting to secondary storage using curl command | It should fail with right message | ||
| T13 | Upload with Invalid File formats | It should fail with right message. Verify the state of the failed upload volume | ||
| T14 | User stopped/canceled the post request before completion | It should fail with right message. Verify the state of the upload volume | ||
| T15 | Upload template failure due to a network issue - Network wentdown on Host where SSVM is running | Verify the state of template | ||
| T16 | Browser request timed out | Verify the error message and state of the volume | ||
| T17 | Browser crashed | Kill the Browser process before upload gets started . Verify the state and error message after Browser is reinitiated | ||
| T18 | SSVM is down/restarted | Verify the state of Upload Templates/Volumes with SSVM restart | ||
| T19 | SSVM apache down/restarted | Verify the state of Upload Templates/Volumes with SSVM restart | ||
| T20 | Secondary storage is not accessible | Verify the state of Upload Templates/Volumes | ||
| T21 | Download Upload Volume and Template when sSVM is not active | Verify the state of Upload Templates/Volumes and ability to download URL | ||
| T22 | There isn't enough space in secondary storage and hence agent can't write to it | Copy a huge disk in to SSVM so that its full and then try upload volume/template | ||
| T23 | Max file size from the header crossed the limit. Koushik to confirm?? | Global config max file size should be honoured | ||
| T24 | SSL handshake failed ( It should have covered with SSVM HA) | Validate the error message and state of volume | ||
| T25 | Params validation with PSK failed ( Tamper the URL testcase should cover) | Validate the error message and state of volume | ||
| T26 | File uploaded is not of the type specified (for ex: if the template is said to be of type tar, the actual downloaded file is not if this type) | Add vhd type file but upload ova . Verify the state of the volume and template . Validate the error message | ||
| T27 | Max upload limit crossed | Verify the state of the volume and validate the error message | ||
| T28 | Upload multiple templates In Parallel | Ensure that template upload works and gets copied to secondary storage with no issues. | ||
| T29 | Upload multiple volumes In Parallel | Ensure that template upload works and gets copied to secondary storage with no issues. | ||
| T30 | Upload Templates and Volumes when Multiple SSVM's present in a single zone | Ensure that template upload works and gets copied to secondary storage with no issues. Have a new SSVM being created because of parallel Browser based volume/template uploads happening and secstorage.session.max limit reached | ||
| T31 | Migrate the errored volume to a same cluster PS | Verify the error message and cleanup | ||
| T32 | Migrate the errored volume to a different cluster Primary storage | Verify the error message and cleanup | ||
| T33 | Migrate the errored volume to a different zonewide Primary storage | Verify the error message and cleanup | ||
| T34 | Try to Cancel the upload inProgress Volume | Verify the error message | ||
| T35 | Try to Cancel the upload inProgress Template | Verify the error message | ||
| T36 | Try to upload volume with invalid md5sum | Verify the error message | ||
| T37 | Upload Template with same name and Display Text | Verify the error message | ||
| T38 | Upload volume with same name and Display Text | Verify the error message | ||
| T39 | Restart Hosts when local storage used for Upload volumes | Local is not supported | Ensure that Upload volumes can be attached/detached/downloaded after host is back to up state | |
| T40 | Reset VM with deleted template ID | Verify the error message and cleanup of worker VMs if any on Vmware | ||
| T41 | POST URL with Deleted Volume | Verify the error message and cleanup of worker VMs if any on Vmware | ||
| T42 | Move the Primary Storage into Maintance mode when shared storage used for volumes | Ensure that Upload volumes can be attached/detached/downloaded after host is back to up state | ||
| T43 | Move the Host into Maintance mode when local storage used for volumes | Local is not supported | Ensure that Upload volumes can be attached/detached/downloaded after host is back to up state | |
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 9: Validation of Required and Optional Parameters in the API request / Response | ||||
| Tests | ||||
| T1 | Upload volume with Project ID | List volumes and verify the details including the project id | ||
| T2 | Upload template with Project ID | List Templates and verify the details including the project id | ||
| T3 | Tag volumes/templates and use list API's to list by matched tags | List Templates by tags and verify the details | ||
| T4 | Validate API calls respone without passing required parameters | Validate the error message | ||
| T5 | Validate API calls respone by passing Invalid required parameters ( Invalid Id, ImageStoreID,diskoffringID,Zoneid,Format) | Validate the error message | ||
| T6 | Upload template with Domain ID | List Templates and verify the details including the Domain ID | ||
| T7 | Upload volume with Domain ID | List volumes and verify the details including the Domain id | ||
| T8 | Upload Templates as ROOT Admin and specify the child domain id | Admin should be able perform template/volume upload for other accounts using account and domainId parameter | ||
| T9 | Upload Templates as Domain Admin and specify the one of the User account in the same domain | Domain Admin should be able perform template/volume upload for other accounts using account and domainId parameter | ||
| T10 | Upload volume as ROOT Admin and specify the child domain id | Admin should be able perform template/volume upload for other accounts using account and domainId parameter | Yes | |
| T11 | Upload volume as Domain Admin and specify the one of the User account in the same domain | Domain Admin should be able perform template/volume upload for other accounts using account and domainId parameter | Yes | |
| T12 | Login as User account and use the Template created by ROOT admin for this use domain to deploy new VM | User account should be able to use the template created by ROOT admin | Yes | |
| T13 | Login as User account and use the Template created by Domain admin for this use domain to deploy new VM | User account should be able to use the volume reated by Domain admin | Yes | |
| T14 | Login as User account and attache the volume created by Domain admin for this user account | User account should be able to use the volume created by ROOT admin | Yes | |
| T15 | Login as User account and attache the volume created by ROOT admin for this user account | |||
| T16 | Upload templates to multiple zones by passing “-1” for zoneId register template | Supported Scenario | Ensure that template gets copied to all zones | |
| T17 | uploadVolume "imagestoreuuid" parameter | |||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 10: Validation of upload volume/template on a Clustered Node Management Server | ||||
| Deploy | ||||
| D1 | Deploy clustered Management node MS with 2 nodes | |||
| D2 | Deploy Zone 2 with Shared Storage added to the deployment (Zone wide primary , Cluster wide Primary) | |||
| Tests | ||||
| T1 | Upload volume and template | |||
| T2 | Deploy VM using this template and add upload volume to this VM | |||
| T3 | Stop MS node where this SSVM is running (Get the MS id of this SSVM from host table) . Upload volume and templates on this SSVM | |||
| T4 | Restart MS node where this SSVM is running (Get the MS id of this SSVM from host table) . Upload volume and templates on this SSVM | |||
| T5 | Stop Ms2 node where SSVM requests are forwarded and get MS1 to up state .Upload volume and templates on this SSVM | |||
| T6 | Issue Browser based volume/template command from a management server that is not the owner of the SSVM , which would result in management server redirecting request to another management server (which is the owner of the SSVM) which needs to communicate with the SSVM to complete the task. | |||
| Cleanup | ||||
| C1 | Delete the account | |||
| C2 | Delete the service offerings | |||
| Test Path 11: Validations Post SSVM Life cycle | ||||
| Tests | ||||
| T1 | Stop and Start SSVM . Perform Upload template and deploy VM with this template | |||
| T2 | Reset VM using this template | |||
| T3 | Reboot SSVM . Perform Upload volume and attach this volume to a VM | |||
| T4 | Live Migrate SSVM to another host. Perform Upload volume and attach , upload template and deploy VM operations | |||
| T5 | Keep the host into maitanance mode where SSVM is running and get it recreated on other host. Perform Upload volume and attach , upload template and deploy VM operations | |||
| T6 | Destory SSVM and wait for the new SSVM creation. Perform Upload volume and attach , upload template and deploy VM operations | |||
| Test Path 12: Performance Test Requirements | ||||
| Tests | ||||
| T1 | Identify the total no of volumes that can be uploaded in Parallel. T | This limits testing is needed for XD | ||
| Test Path 13: Regression Testing (Upload volumes, Extract template, Extract volume ) | ||||
| Tests | ||||
| T1 | Validate upload volume | |||
| T2 | Download volume | |||
| T3 | Download template | |||
summary
| Ref | Test Step | Total Tests |
| Hypervisor - Vmware,KVM,XenServer,HyperV , Storage - NFS,iSCSI(Vmware) , SMB(HyperV) , Guest OS - Windows 8 , Win 2012 , RHEL 6.5 , Storage- Local, Shared , Account - Root Admin , User , Domain Admin | ||
| Test Path 1: Browser Based Volume Life Cycle | 38 | |
| Test Path 2: Browser Based Template Life Cycle | 19 | |
| Test Path 3: Browser Based Volume Storage Migration | 14 | |
| Test Path 4: Storage Global Config Parameters Validation | 6 | |
| Test Path 5: Browser based Volume , Template Resource Limits validation | 10 | |
| Test Path 6: Usage Validation for Browser Based Volumes and Templates | 2 | |
| Test Path 7: Upgrade | 7 | |
| Test Path 8: Negative Testing | 43 | |
| Test Path 9: Validation of Required and Optional Parameters in the API request / Response | 17 | |
| Test Path 10: Validation of upload volume/template on a Clustered Node Management Server | 6 | |
| Test Path 11: Validations Post SSVM Life cycle | 6 | |
| Test Path 12: Performance Test Requirements | 1 | |
| Test Path 13: Regression Testing (Upload volumes, Extract template, Extract volume ) | 3 | |
| Total | 172 | |
Overview
Content Tools