What is Testopia and How to set access control in Testopia at Test Plan Level?


What is Testopia?

Testopia is a test case management extension for Bugzilla. This allows a single user experience and point of product management for both defect tracking and test case management. It is designed to be a generic tool for tracking test cases, allowing for testing organizations to integrate bug reporting with their test case run results.
Bugzilla is one of the most popular open source issue tracking systems available. Testopia integrates with Bugzilla products, components, versions, and milestones to allow a single management interface for high level objects. Testopia allows users to attach bugs to test case run results for centralized management of the software engineering process.
Testopia allows users to login to one tool and uses Bugzilla group permissions to limit access to modifying test objects.

What is Testopia and How to set access control in Testopia at Test Plan Level?


Test Plans:
At the top of the Testopia hierarchy are test plans. So you need to create a Test Plan before you can do anything else in Testopia. Test plans are associated with a single product in Bugzilla. You can create multiple test plans for each product. This test plan will use as the storage point for all related test cases and test runs and it will act as the dashboard for your testing. It will also determine who will have access to update test cases.

What is Testopia and How to set access control in Testopia at Test Plan Level?


Test Cases:
Test cases are semi-independent in Testopia. Each test case can be associated with multiple test plans. Test cases are associated with one or more test plans and with zero or more test runs. Test cases can be divided into categories. You can define as many categories for your product as you like from the test plan page. Each product in Bugzilla is divided into components and you can apply multiple components to each test case, however each test case can only belong to one category at a time.

What is Testopia and How to set access control in Testopia at Test Plan Level?


Test Runs:
Once you have defined a set of test cases, you are ready to run through those tests in a test run. Each run is associated with a single test plan and Environment. It contains any number of test cases from that plan. It contains a list of test cases to be examined and stores the results in the case-runs table.

What is Testopia and How to set access control in Testopia at Test Plan Level?


Test Case-run:
The union of a test case and a test run. Each time a test case is included in a new test run, an entry is made for it in the test case-runs table. This captures whether the test case passed or failed in the given run. Each case-run should be associated with only one build for a given status.
When you create a test run, records for each test case in that run are created. By default these take on the build and environment of the test run, however, it is possible to change these attributes on a particular case-run, essentially creating a new case-run for each combination.

What is Testopia and How to set access control in Testopia at Test Plan Level?



How to set access control in Testopia at Test Plan Level?

When you first install Testopia, it will create a Bugzilla group called “Testers”. Members of this group have access to view and update all test plans and their associated objects such as cases and runs. Membership in this group is required in order to create new test plans, clone test plans, and administer environments. If the “testopia-allow-group-member-deletes parameter” is on, members of this group will also have rights to delete any object in Testopia. Membership in this group is checked first and supersedes the access control lists for individual plans.

Testopia checks which test plans your user has access to / remember access control in testopia is at the test plan level (Permissions tab in a test plan). Testopia checks if all the test plans to which the user can access are associated with products that the user has access to. If not then it complains: "You are not authorized to edit product X contact administrator etc."

In addition to the Testers group, each test plan maintains it's own access control list which can be used to allow or deny access to test plans based on email domain or explicit inclusion. Each test plan has its own access list. For a user that is not in the Testers group to access a test plan or any associated cases, runs, or case runs, he or she must be included on the list either by matching a regular expression, or explicit inclusion. To edit the access control list for a plan, navigate to the test plan and click the Permissions tab.

What is Testopia and How to set access control in Testopia at Test Plan Level?


User Regular Expression:
Users with login names (email addresses) matching a supplied regular expression can be given rights to a particular test plan. The regular expression should be crafted with care to prevent unintentional access to the test plan by outsiders.

For example :
To grant access to your test plan by all users at SoftwareTestingDiary.com you would supply the following regular expression:
^.*@SoftwareTestingDiary\.com$
To provide access to all users at gmail.com and SoftwareTestingDiary.com you would use:
^.*@(gmail\.com|SoftwareTestingDiary\.com)$
To provide public access (all users) you would use:
.*
An empty regular expression does not match anything meaning leaving this field blank will mean the test plan will rely solely on explicit membership. Once you have supplied the regular expression, you must select the access level.

Explicit Inclusion:
If you do not wish to grant access to a whole group at once, you can add individual users by entering their Bugzilla login id in the field provided and clicking the Add User button. This allows the most fine grained control as to who can do what within your test plan. However, if you add a user that matches the regular expression they will have the greater of the two rights.

Access Rights
Users on the test plan access control lists can be granted rights to read, write, delete, and admin test plans and their associated objects.

Read: Allows viewing rights to the plan and all test cases, test runs, and test case-runs associated with it. Test cases linked to more than one plan will be visible to users in both plans.
Write: Implies Read. Allows rights to modify the plan and associated cases, runs, and case-runs. Test cases linked to more than one plan will not be writable unless the user has write rights in all plans.
Delete: Implies Read and Write. Allows rights to delete the plan and associated cases, runs, and case-runs. Test cases linked to more than one plan will not be deletable unless the user has
delete rights in all plans.
Admin: Implies Read, Write, and Delete. Allows rights to modify the plan's access controls.








Thanks and Regards,
Prashant Vadher | QC Engineer

0 Comments:

Post a Comment

 
Design by Prashant Vadher