Litmus:Admin Tutorial: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
* Update the information for the user as necessary and then click on  "Submit changes."
* Update the information for the user as necessary and then click on  "Submit changes."


== User Flags and Values ==
== Flags and Values ==
* Enabled: if a user account is not enabled, they cannot login and run tests. User accounts are enabled by default.
* Enabled: if a user account is not enabled, they cannot login and run tests. User accounts are enabled by default.
* Is an admin?: Admin users can edit everything, including other users.
* Is an admin?: Admin users can edit everything, including other users.
Line 15: Line 15:


== Adding a testcase ==
== Adding a testcase ==
Fill in all of the required information for the new testcase.
Steps to perform/Expected Results: be as specific yet concise as possible. Remember that the people who will be running this test will not necessarily be as familiar with Mozilla processes and internals. If terms or concepts need clarification, hyperlink them to an appropriate information source rather than explaining them inline. This will help reduce the size of the testcase and hopefully make it less daunting to testers.
Enabled: disabled testcases will not appear in test lists, except in the Manage Testcases interface or when accessed explicitly.
Community Enabled: Only testcases that are community enabled can be seen by the community when tests are being run. This flag will not affect the view for admin users, i.e. admin users will always all tests regardless of this flag.
NOTE: Once a new testcase is added, you need to add it to a subgroup as a separate step.


== Edit, Clone, and Delete ==
== Edit, Clone, and Delete ==

Revision as of 20:21, 12 April 2007

User Management

  • In the left-hand sidebar, click on the Manage Users link.
  • Enter your search criteria in the search box and submit.
  • Select the user you would like to edit from the list of returned users. Click on edit in the left-hand column to edit that user.
  • Update the information for the user as necessary and then click on "Submit changes."

Flags and Values

  • Enabled: if a user account is not enabled, they cannot login and run tests. User accounts are enabled by default.
  • Is an admin?: Admin users can edit everything, including other users.
  • Web services auth token: A web services auth token allows that user to submit testing results via web services (XML-RPC). In general, we should encourage users who are going to submit results via web services (likely automated results) to setup a separate account for submitting those results.

Testcase/Subgroup/Testgroup Management

Adding a testcase

Fill in all of the required information for the new testcase.

Steps to perform/Expected Results: be as specific yet concise as possible. Remember that the people who will be running this test will not necessarily be as familiar with Mozilla processes and internals. If terms or concepts need clarification, hyperlink them to an appropriate information source rather than explaining them inline. This will help reduce the size of the testcase and hopefully make it less daunting to testers.

Enabled: disabled testcases will not appear in test lists, except in the Manage Testcases interface or when accessed explicitly.

Community Enabled: Only testcases that are community enabled can be seen by the community when tests are being run. This flag will not affect the view for admin users, i.e. admin users will always all tests regardless of this flag.

NOTE: Once a new testcase is added, you need to add it to a subgroup as a separate step.

Edit, Clone, and Delete

  • You can use the filter criteria to narrow the list of displayed testcases.
  • Select the testcase you want to clone or delete.
  • Verify from the displayed information that the testcase you have selected is the one you want to clone/delete.
  • Confirm your action in the resulting dialog.

NOTE: when cloning a testcase, all of the existing relationships, e.g. subgroup membership, will be propagated to the new testcase. You will need to edit the new testcase to remove or alter those linkages if they are not accurate.

Test Run Management