Page Comparison

...

You must have administrative access to your Qualitia Automation Studio (QAS) to manage roles and assign users to roles.

Qualitia implements role-based security for users. Roles are based on functionality of users like Testers, Automation Test Engineers, and so on. Appropriate privileges are assigned to the roles.

QAS contains the following five pre-defined roles assigned with specific Qualitia privileges as described below. 

1. Admin: Admin will have all the privileges.

2. Project Manager: Project Manager will have all the privileges except Create Project.

3. Custom Action Developer: Custom Action Developer should have the following privileges:

   1. Manage Custom Action 

   2. Manage Objects

   3. Synchronize Objects

   4. Test Development

   5. Test Execution

4. Test Lead: Team Lead should have:

   1. Manage Scenarios

   2. Synchronize Objects

   3. Test Development

   4. Test Execution

   5. Manage Suites

   6. Import Artifacts

   7. Manage Custom Actions 

   8. Manage Objects

5. Tester: Tester should have:

   1. Manage Objects

   2. Synchronize Objects

   3. Test Development

   4. Test Execution

🔀 Procedural Steps

In this section, we will cover the step-by-step guide to create and manage roles.

...

1. Login to QAS - Client.

2. Access User Management from left navigation of your QAS - Client.

   1. Clicking User Management takes you to the User & Role Management screen.

3. By default, you land on the Users tab.

   1. Here you can view the existing users.

4. Click Roles to manage roles and view available roles. 

5. Click +Create Role from the top-right corner of the Roles screen. You will see a popup window.

   1. Enter the role name in the Role field.

   2. Enter a brief role description in in the Description field.

   3. Under Assigned Privileges section, select the checkboxes to assign the privileges.

   4. Click Save to continue; otherwise, click Discard.

6. Repeat the steps 2 through 5 for each additional role you want to add.

...

• Activate Deactivate Projects: Activate or deactivate a project.

• Create Project: Create a project.

• Import Artifacts: Import test artifacts or other project elements.

• Manage Custom Actions: Develop, addAdd, edit, or delete a custom action.

• Manage Objects: Control the objects within your testing environment.

• Manage Projects: Oversee all aspects of your projects.

• Manage Roles: Assign and modify user roles.

• Manage Scenarios: Control the scenarios within your test suites.

• Manage Suite: Add, edit, or remove suites.

• Manage Users: Oversee user access and privileges.

• Synchronize Objects: Import and export objects from TSR (Desktop projects only).

• Test Development: Create, update, and record test cases and tasks.

• Test Execution: Edit & publish suits. Publish test cases. 

🔎 View Roles

1. Login to QAS - Client.

2. Access User Management from left navigation of your QAS - Client.

   1. Clicking User Management takes you to the User & Role Management screen.

3. By default, you land on the Users tab, where you can view the existing users.

4. Click Roles to open the Roles screen.

   1. The Roles screen displays the following two sections:

      1. Roles: You can see all the existing QAS Roles.

         1. By default, the first Role in the Roles section is selected.

      2. Role Details: You can view role Description, Assigned Privileges, and the Assigned Users.

...

• Unique Roles: Each role should be distinct and specific to a set of responsibilities. This prevents overlap and confusion.

• Avoid Overloading: Avoid loading a role with too many privileges. The principle of least privilege should be followed - assign only necessary rights to a role.

• Memorable Yet Secure: Role names should be intuitive and easy to remember, but not too predictable to avoid potential security risks.

• Ideal Length: A role name that is too short may lack clarity, while a long one may be hard to remember. Aim for a sweet spot between 6 to 14 characters.

• Special Characters? Think Twice: Avoid special characters in the role name instead use your creativity to provide a better name.

• Consistent Naming Convention: Managing multiple roles? Having a consistent naming structure can simplify management and identification.

• No Offensive Language: Ensure the role names are professional and respectful.

• Regular Audits: Review roles and their privileges regularly to maintain security and prevent unauthorized access.

• Delete: Need to temporarily suspend a role? Remove users from the role instead of deleting it. If the role is no longer needed, then consider deletion. 

...