Test Cases For User Roles And Permissions

Test Cases For User Roles And Permissions: When we are focussing on website development, user roles and permissions are an important way of controlling access to the site. This is important when there are multiple individuals besides the website owner who administers the site. Other people can be assigned certain ‘roles’ which define the kind of access that is to be granted.

Basically, the Site maintainer and Administrator roles are given all the available permissions and the Administrator role receives all permissions throughout the lifespan of the site. This is not the case for other ‘roles’, where access within admin permissions and time limits only are granted to users linked to those roles.

A major advantage of adding permissions is that, when a new feature is added to a domain that is not allowed for everyone by default, this functionality can be made specifically for a ‘role’ or a group of ‘roles’ but grants access to them alone. Roles are not just a way to group permissions, but they also hide important information about the site as well.

For this reason, users, roles, and their permissions are imperative and have to be set up and configured appropriately, and tested systematically. The major Test cases/checklists to be considered while testing roles and permissions are documented here.

Similar Test Cases

• Test Case For Tabs
• Test Case For Testing Video Frames
• Test Case For User Registration Form
• Test Case For Video Streaming Application
• Test Case For Web Application
• Test Case For Yahoo Registration Page

Test Cases For User Roles And Permissions

• Check the domain allows for creating new users with the role(s) For this
  • Create a test account and assign the created role to it.
  • Then log in as the new user and ensure all privileges are given to that role.
  • Alternatively, use a different browser (not a new window in the same browser) to test the role without logging out as an administrator.
  • Repeat the above steps for all roles and permissions on the site.
    
    In case a new role arises as a requirement while handling a maintenance site or after the completion of the site, then it has to be tested extensively before being assigned to any user. The above procedures are to be repeated in such cases as well.

• Check is the permissions granted to custom roles are working as expected.
• Check if the “access denied” error message is shown when
  • Anonymous or nonpermitted users attempt to view a resource that is granted only to certain roles.
  • Anonymous or nonpermitted users attempt to access a page/URL that is restricted to them.

• In case a user has more than one role, ensure that multiple roles and the combinations of those permissions (same user with conflicting permissions) work correctly.
• Check if the Admin can mark/unmark permissions for users via the permissions page and these changes get reflected in the user’s role as well.
• Check if the user does not have access to permissions once these permissions are taken out from the user’s role.

Conclusion:

We hope this article will surely help you in understanding how to write the Test Cases For User Roles And Permissions. If you want to add some missing scenarios then you can comment in the comment section and we will update accordingly.