Administration¶
The TCMS Administration tab allows administrators to manage:
Entities
Group and user permissions
Test Plans and Test Cases.
Managing Permissions¶
The Auth administration section covers Groups and Users.
Groups¶
Nitrate uses groups to manage access to parts of the system. Groups have two fields: name and permissions. By default there are three groups created:
Tester
: has necessary permissions to operate plans, cases, runs, comments and other routine works.Administrator
: has a superset of Tester’s permissions to allow delete operation.System Admin
: has dedicated permission to change user’s information.
Adding a group¶
A group requires a name and a set of permissions.
Procedure: Adding a group¶
To add a group:
From the ADMIN menu, click Auth.
Click Groups, then click Add Group.
In the add group screen, perform the following actions:
Enter the Group Name.
From Available permissions, select the Group’s permissions.
Click Add.
The Chosen permissions list is updated.
Click Save.
Users¶
Assigning administrator rights¶
A user with administrator rights can access the ADMIN tab.
Procedure: Assigning administrator rights¶
To assign administrator rights:
From the ADMIN menu, click Auth.
Click Users.
In the Search Bar, enter the username, and then click Search.
Click the Username.
In the Permissions screen, select Staff status.
Click Save. The Staff Status icon changes to a green tick.
Note
If the user requires full permissions, select Superuser status.
Assigning Permissions¶
User permissions can be granted or revoked for individual components of
Nitrate. All permissions are prefixed with the add_
, change_
and
delete_
prefixes signifying the operation which is controlled by this
permission. Then the codename contains the name of the model for which this
permission applies. For example, the ability to add attachments to a Test Case
is controlled via the add_testcaseattachment
permission.
Procedure: Assigning Permissions¶
To assign permissions:
From the ADMIN menu, click Auth.
Click Users.
In the Search Bar, enter the username, and then click Search.
Click the Username.
In the User permission screen:
To add permissions, select the permissions to be granted, and then click Add.
To remove permissions, select the permissions to be revoked, and then click Remove.
Click Save.
Adding a user to a group¶
Group permissions in Nitrate work the same as they do in Linux. The system checks a user’s personal permissions, then group permissions.
Procedure: Adding a user to a group¶
To add a user to a group:
From the ADMIN menu, click Auth.
Click Users.
In the Search Bar, enter the username, and then click Search.
Click the Username.
From Groups select the user to add.
Click Save.
Updating personal information¶
Nitrate can store email, first and last name details of a user.
Procedure: Updating personal information¶
To update personal information:
From the ADMIN menu, click Auth.
Click Users.
In the Search Bar, enter the username, and then click Search.
Click the Username.
From Personal Information edit:
First Name
Last Name
Email Address
Click Save.
Deleting a user¶
Users can not be deleted from Nitrate. A user that is no longer required must be disabled.
Procedure: Disabling a user¶
To disable a user:
From the ADMIN menu, click Auth.
Click Users.
In the Search Bar, enter the username, and then click Search.
Click the Username.
Untick the Active checkbox.
Click Save.
Access Control Lists¶
Nitrate uses ACLs for the user groups: Guest, Tester, and Admin. The permissions for each group can be controlled from the Group section in the AUTH tab.
Default ACLs in the TCMS.
Group |
Test Plan |
Test Case |
Environment |
Administration |
---|---|---|---|---|
Guest |
Read |
Read |
||
Tester |
Read / Write |
Read / Write |
Read / Write |
|
Administrator |
Read / Write |
Read / Write |
Read / Write |
Read / Write |
Managing entities¶
The following entities are listed in Nitrate:
Builds
Classifications
Components
Priorities
Products
Versions
Builds¶
The entity build describes the operating system version (build) used for Test Cases. This is particularly important to help ensure Test Cases are repeatable.
Procedure: Adding a build¶
To add a build:
From the ADMIN menu, click Management.
Click Builds.
Click Add build.
In the Add build screen, perform the following actions:
Enter Name.
Select Product.
Enter build Description.
Click Save.
Editing a build¶
The name, product, and is active fields can be edited.
Procedure: Editing a test build¶
To edit a test build:
From the ADMIN menu, click Management.
Click Test Build.
Click the ID of the Test Build to be edited.
In the Change Test Build screen edit the following:
Name
Product
Description
Is active
Click Save.
Classifications¶
A classification is a title used to group products of a similar nature. For example, Red Hat, Fedora, Internal Infrastructure.
Procedure: Adding a classification¶
To add a classification:
From the ADMIN menu, click Management.
Click Classifications.
Click Add classification.
In the Add classification screen, perform the following actions:
Enter the Name.
Enter a Description.
Enter the Sortkey.
Click Save.
Editing a classification¶
The name and description fields can be edited.
From the ADMIN menu, click Management.
Click Classification.
Click the ID of the classification to edit.
In the Change classification screen edit the following:
Name
Description
Sortkey
Click Save.
Components¶
A product is broken down into components. For example, two components of RHEL 5 are glibc and gdm.
Procedure: Adding a component¶
To add a component:
From the ADMIN menu, click Management.
Click Components.
Click Add component.
In the Add component screen, perform the following actions:
Enter the Name.
Select the Product.
Select the Initial owner.
Select the Initial QA contact.
Enter the component Description.
Click Save.
Note
Creating entries To create the fields Product, Initial Owner, or Initial QA Contact, click the green plus icon.
Editing a component¶
The fields name, product, initial owner, QA contact, and description can be edited.
Procedure: Editing a component¶
To edit a component:
From the ADMIN menu, click Management.
Click Component.
Click the ID of the component to be edited.
In the Change component screen edit the following:
Name
Product
Initial Owner
Initial QA contact
Description
Click Save.
Priorities¶
Test Cases can be assigned a priority.
Adding a priority¶
The priority field is alphanumeric.
Procedure: Adding a priority¶
To add a priority:
From the ADMIN menu, click Management.
Click Priorities.
Click Add priority.
In the Add priority screen, perform the following actions:
Enter the Value.
Enter the Sortkey.
Click Is active.
Click Save.
Editing a priority¶
All three attributes of a Priority can be edited.
Procedure: Editing a priority¶
To edit a priority:
From the ADMIN menu, click Management.
Click Priorities.
From the Id column, click the priority to edit.
In the Change priorities screen, edit the following:
Value
Sortkey
Is active
Click Save.
Products¶
All testing is based around the products made by Red Hat.
Procedure: Adding a product¶
To add a product:
From the ADMIN menu, click Management.
Click Products.
Click Add product.
In the Add product screen, perform the following actions:
Enter the Name.
Select the Classification.
Enter the product Description.
Click Disallow New.
Select the Votes Per User.
Enter the Max Votes Per Bug.
Click Votes To Confirm.
Click Save.
Editing a product¶
The fields name, classification, description, disallow new and votes to confirm can be edited.
Procedure: Editing a product¶
To edit a product:
From the ADMIN menu, click Management.
Click Products.
Click the ID of the product to be edited.
In the Change product screen, edit the following:
Name
Classification
Description
Disallow New
Votes To Confirm
Click Save.
Versions¶
Each product in Nitrate needs a version. Many products will have multiple versions. For example, Firefox 3.0.14, 3.5.3.
Procedure: Adding a version¶
To add a version:
From the ADMIN menu, click Management.
Click Versions.
Click Add version.
In the Add version screen, perform the following actions:
Enter Value.
Select Product.
Click Save.
Managing Test Plans¶
This section covers the administration of meta data relating to Test Plans.
Test Plan types¶
A Test Plan type is used to describe the test being performed. For example, acceptance or smoke.
Adding a Test Plan type¶
A new type needs a name, and description.
Procedure: Adding a Test Plan type¶
To add a Test Plan type:
From the ADMIN menu, click Test Plans.
Click Test Plan Categories.
Click Add Test Plan Types.
In the Add test plan type screen, perform the following actions:
Enter the Name.
Enter the type Description.
Click Save.
Test plans¶
This screen provides a list of all the test plans in Nitrate. The Add test plan link can be used to create a test plan. For more information, see Creating a Test Plan.
Managing Test Cases¶
This section covers the administration of meta data relating to Test Cases.
Test Case Bug Systems¶
The bug system for test cases is Red Hat Bugzilla. To view the details click the Test case bug systems.
Test Case categories¶
A category is used to describe the type of test being performed. For example, regression or bug verification.
Adding a Test Case category¶
A new category needs a name, product and description.
Procedure: Adding a category¶
To add a category:
From the ADMIN menu, click Test Cases.
Click Test case categories.
Click Add Test Case Category.
In the Add test case category screen, perform the following actions:
Enter the Name.
Select the Product.
Enter the category Description.
Click Save.
Test cases¶
This screen provides a list of all the test cases in Nitrate. The Add test case link can be used to create a test case. For more information, see Creating a Test Case.