Roles and Permissions Page - QA Test Plan
On this page
Role Create / Update / Delete
Test A: Check that the TENANT_ADMINISTRATOR and _READER roles are displayed properly
Actions:
- Login with full privileges
- Go to Administration in the top menu navigation, then the Roles and Permissions tab
Expected:
- The TENANT_ADMINISTRATOR and TENANT_READER roles should be displayed on the list to the left
Actions:
- Click the TENANT_ADMINISTRATOR role
Expected:
- The Role name should be displayed
- All permissions should be set to Delete
- The permissions should be read only
Actions:
- Click the TENANT_READER role
Expected:
- The Role name should be displayed
- All permissions should be set to Read
- The permissions should be read only
Test 1: Create New Invalid Role - No Role Name
Actions:
- Login with full privileges
- Go to Administration in the top menu navigation, then the Roles and Permissions tab
- Click the + Create new button on the left
Expected:
- A new role form should appear
- All permissions should be set to None
Actions:
- Click save
Expected:
- A message will appear reading, "Name is required. Please enter a value."
Test 3: Create New Valid Role
Actions:
- Continue from Test 1
- Fill out Name
- Change any of the permission settings
- Click save
Expected:
- The new role should be displayed on the list
- A successful save message should display
Actions:
- Click a different role
- Wait for it to load
- Click back to the role you created
Expected:
- The Name, Description and Permissions should be as you created them
Test 5: Create New Invalid Role (Duplicate Role Name)
Actions:
- Continue from Test 3
- Click the + Create new button on the left
- Fill out the Name with the same name as an existing role
- Click save
Expected:
- A message should appear telling you that duplicate role names are not allowed
- The new role should not be saved
Test 9: Edit Existing Role to Invalid
Actions:
- Continue from Test 7
- Select a role that you can edit by clicking on it in the left menu
- Change any permissions of that role
- Delete the text from Name
- Click save
Expected:
- A message reading "Name is required. Please enter a value." should appear
- No save should take place
Actions:
- Change the role name to be the same as an existing role
- Click save
Expected:
- An error message should appear in the bottom of the screen
Test 11: Edit Role (Valid)
Actions:
- Continue from Test 9
- Change the value in the Name field
- Change the Description
- Change any permissions of the role
- Click save
Expected:
- The name in the left list should change to the new name
- Navigate away from the role by clicking another role, then back to the one you edited
- The Name, Description and Permissions should reflect your changes
Test 13: Delete Role with Cancel/Close
Actions:
- Continue from Test 11
- Click the Delete button above the Role form
Expected:
- A confirmation dialog should appear
Actions:
- Variation A: click Cancel
- Variation B: click Close symbol
- Variation C: hit the Escape key
Expected:
- The dialog should be dismissed
- Form should be unchanged
Test 15: Successfully Delete Role
Actions:
- Continue from Test 13 (or select a role you are comfortable deleting)
- Click the Delete button above the Role form
- In the dialog, hit delete
Expected:
- The dialog should be dismissed
- A Role successfully deleted message should appear
- The role should disappear from the list of roles
Test 17: Delete Role Assigned to User
Actions:
- Create a new role
- Take a note of the name of the role
- Go to the Users tab
- Create a new user
- Assign your newly created roll to the new user by marking the role in the Roles list
- Click Save
- Go to Roles and Permission tab
- Select the role you created from the list to the left
- Click the Delete button
Expected:
- An pop-up error message should tell you "(Role Name) cannot be deleted because it is associated with user accounts."
- The role should still be in the form as well as in the list to the left
Test 20: Spend 5 minutes trying to break something!
- Spend a few minutes forcing the program to expose buggy behavior by:
- using the system in ways not covered by the testplan
- using the system in unexpected ways
- doing whatever you can think of that will produce bugs and unexpected behavior.
- Be creative!