Test case Id | Test case description | Steps | Expected Result | Priority | Status | Comments |
---|---|---|---|---|---|---|
1. | Verify Global configuration | 1. Set configuration to true | In both 2 and 3 project creation should be successful | P1 | pass |
|
2. | Verify Global configuration | 1. Set configuration to false | In 2 project creation should be successful | P1 | pass |
|
3. | Verify Global configuration | 1. Set configuration to false | Verify after step 3 user is added to project as regular user | P1 | pass |
|
4. | Verify Global configuration | 1. Set configuration to true | Verify after step 3 user is not added to project as regular user | P1 | pass |
|
5. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation is accepted and user become regular user of project | P1 | pass |
|
6. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation is not accepted and shown as expired | P2 | pass |
|
7. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation send again | P3 | pass |
|
8. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation is rejected and user does not become regular user of project | P1 | pass |
|
9. | Verify Global configuration | 1. Set configuration to 5 mins | Verify after step 3 user is not added to project as regular user | P2 |
|
|
10. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation is accepted and user become regular user of project | P2 |
|
|
11. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation is not accepted and shown as expired | P2 |
|
|
12. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation send again | P2 |
|
|
13. | Verify Global configuration | 1. Set configuration to 5 mins | Verify invitation send again | P3 |
|
|
14. | Verify an account can own multiple projects and can belong to multiple projects | 1. Create multiple project | Verify at step 1 An account is allowed to create multiple projects | P1 | pass |
|
15. | Verify No cross domain projects | 1. Create a project in a domain | After step 2 Verify account addition fails | P1 | pass |
|
16. | Verify As long as the project exists, its owner can't be removed | 1. Create a Project | After step 2 delete account should fail | P1 | pass |
|
17. | Verify delete domain with cleanup=true should delete projects belonging to the domain | 1. Create a project in a domain | After Step 2 Projects belonging to this domain should also be deleted as a part of domain cleanup | P2 | pass |
|
18. | Verify a project user can be later promoted to become a owner | 1. Create a Project | After step 3 new account should be the project owner and the old owner should be now a project user | P1 | pass |
|
19. | Verify there can only be one owner of a project at a time | 1. Create a Project | After step 4 making another user also project owner should fail | P2 | pass |
|
20. | Verify after an account is removed from the project, all his resources stay with the project. | 1. Create a Project | After step 4 verify all the resources of project is still there with the project | P1 | pass |
|
21. | Verify project deletion | 1. Create a Project | Verify after step 4 all the resources belonging to project is released and freed. | P1 | pass |
|
22. | Verify Project Suspension | 1. Create a Project | Verify all running VM stops | P1 | pass |
|
23. | Verify Project activation after its Suspension | 1. Create a Project | Verify project is activated after step 5 | P2 | pass |
|
24. | Verify change views | 1. Create a Project | After Step 4 Only resources related to account is shown | P1 | pass |
|
25. | Verify user is presented list of all the projects he belongs to “view” into. | 1. Create several projects | after step 3 a list of all the projects belonging to this account should be shown | P1 | pass |
|
26. | Project Limits | 1. Create a Project | After step 1 Verify once projects are created, they inherit a default set of resource limits as configured by the Cloud Stack ROOT admin. | P1 | pass |
|
27. | Project limits | 1. Create a Project | After step 2 resource count should be updated | P3 | pass |
|
28. | Project Limits :VMs | 1. Create a Project | After step 3 resource allocation should fail giving proper message | P1 | pass |
|
29. | Project Limits :snapshots | 1. Create a Project | After step 3 resource allocation should fail giving proper message | P1 | pass |
|
30. | Project Limits :Volumes | 1. Create a Project | After step 3 resource allocation should fail giving proper message | P1 | pass |
|
31. | Project Limits :IP | 1. Create a Project | After step 3 resource allocation should fail giving proper message | P1 |
|
|
32. | Project Limits :Templates | 1. Create a Project | After step 3 resource allocation should fail giving proper message | P1 |
|
|
33. | Resource creation -ServiceOffering/DiskOffering* * | 1. Create a Project | After step 2 All DO/SO available in the domain can be used for project resource creation. | P1 |
|
|
34. | Resource creation -Network | 1. Create a Project | Verify any number of Project level Virtual/Direct networks can be created and used for vm deployment within the project. | P1 | pass |
|
35. | Resource creation -Template | 1. Create a Project | Verify only Public templates can be used without any restrictions by Project. | P1 |
|
|
36. | Resource creation -Snapshot | 1. Create a Project | Verify only snapshot created within the project can be used by the project | P1 | pass |
|
37. | Resource creation -IpAddress | 1. Create a Project | Verify only ip address created within the project can be used for PF/LB/Firewall rules creation within the project. | P1 |
|
|
38. | Resource creation -PF/LB/VPN rules | 1. Create a Project | Verify when rule is creating in the project, it can be mapped only for vm/IP belonging to the project | P1 |
|
|
39. | Resource creation -Security groups in Basic zone | 1. Create a Project | Verify if rule is created in the project, it can be assigned only to the vm belonging to the project | P1 |
|
|
40. | Verify usage for projects | 1. Create a Project | After step 2 Verify all the usage generated for the resources belong to the project | P1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|