Software Development: Testing

Needs the Software development module. Open Testing in the Software Development menu in the left sidebar. The Testing page has three tabs along the top: Library, Plans & runs and My tests.

Library

The test cases, by product, module and suite, with their steps. Admins and people with the QA flag edit them; a spreadsheet can be uploaded. The Library opens on All products (with a Product column); pick a product to narrow it and see its suites. In a window narrower than about 1100 px, the Module, Type, Tags and Version columns are hidden so the table fits.

Plans & runs

A plan is a set of cases (picked by hand, by a saved filter, or copied from the last plan). A run is one pass of a plan: each case is pinned to the version it had when the run started, and is assigned to a tester.

A run's page lists its cases and their results, and Issues found: the issues its failed steps opened.

My tests

(Formerly "My cases".) Two lists:

• Your cases: the run cases assigned to you. Open one to execute it: mark each step Pass, Fail, Blocked or Skip, add notes and screenshots, and log your time.
• To re-test: issues you test that reached the Board's Testing column (status resolved).
• Workspace without Mantis: Pass closes the issue (Done: resolution fixed, fixed in its target version). Fail reopens it (resolution reopened, back to In progress for the developer).
• Mantis workspace: the issue lives in Mantis; use Close in Mantis or Reopen in Mantis. It leaves the list once Mantis's copy shows it is no longer resolved.

Both lists also show on your My Tasks board and the My tasks panel of My Day: one card per run with cases left (Test run #3: 4 of 12 cases left, linking to the next case to execute) and one Re-test card per issue to re-test (linking here). A run's card leaves when every case of yours in it has a result; a re-test card leaves on Pass or Fail.

A failed step is a Bug

• Workspace without Mantis: failing a step opens a Bug issue on its own (one per step), linked to the test case and the run, with the steps and your note in its description. You are its tester, so it comes back to your To re-test list once it is fixed.
• Mantis workspace: Otium never writes to Mantis. The execute screen shows Report in Mantis: a Mantis new-issue page pre-filled with the case, its steps and the result. Submit it in Mantis, then paste the number Mantis gives it into Link on the same screen. The run keeps the number, the issue shows the run on Issues, and it reaches your To re-test list when Mantis marks it resolved.

Issues list the test runs that found them (the Test runs column on Issues, and the issue page for native issues).