81
edits
TestEngineering/Testrail: Difference between revisions
→Access and Permissions
StuartPhilp (talk | contribs) |
StuartPhilp (talk | contribs) |
||
| Line 3: | Line 3: | ||
=== Access and Permissions === | === Access and Permissions === | ||
'''Testrail is currently an internal Mozilla tool'''. It is behind our VPN and requires | '''Testrail is currently an internal Mozilla tool'''. It is behind our VPN and requires an 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. | 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 | 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 one of the Testrail administrators. | ||
=== Testrail Administrators === | === Testrail Administrators === | ||