81
edits
TestEngineering/Testrail: Difference between revisions
→What is testrail?
StuartPhilp (talk | contribs) |
StuartPhilp (talk | contribs) |
||
| Line 1: | Line 1: | ||
== What is testrail? == | == What is testrail? == | ||
Testrail is a test case management tool used by most QA teams at Mozilla to catalog and track test cases over the life of a project (including versions/releases/features). Testrail is the single source of truth for all testing data (test plans, reports, failures, etc.) and so is an important component in the overall software life cycle at Mozilla. | Testrail is a test case management tool used by most QA teams at Mozilla to catalog and track test cases over the life of a project (including versions/releases/features). Testrail is the single source of truth for all testing data (test plans, reports, failures, etc.) and so is an important component in the overall software life cycle at Mozilla. | ||
=== Access and Permissions === | |||
'''Testrail is currently an internal Mozilla tool'''. It is behind our VPN and requires and LDAP account to log in. We are working on a solution for community/public access which would allow anyone to review our test plans and progress. For progress on community access you can subscribe to the [https://lists.mozilla.org/listinfo/dev-quality dev-quality] mailing list, or check back on this page. | |||
Testrail has a hierarchical permission structure based on who can view/edit/update any given project and test suite. By default all new users have '''read-only''' permissions. | |||
We have defined a set of projects and groups to allow easier management of these permissions. If you want edit access to a specific project you will need to be a member of the team(s) responsible for that project. To get edit-access to a project please contact on of the Testrail administrators. | |||
== Writing a test plan == | == Writing a test plan == | ||