Skip to content
Start

Test management overview

Test management is where your team keeps its manual tests and their results. You write each check once as a test case with its preconditions, steps and expected result. You group cases into test suites, collect the ones you run often into test plans, and record each round of testing as a test run.

Lumen Labs keeps its app tests in the Lumen QA project: suites for Onboarding, Offline maps, Light and weather and Trips, a Smoke test and a Beta 1.0 regression plan, and a run for each beta build.

Open Test management from the left rail.

The Lumen QA test library with the project's Test library, Test plans and Test runs links, the suites, the cases grouped by suite, Run and New test case marked
  1. Each project has a Test library, Test plans and Test runs.
  2. The Test suites pane lists the suites as a tree. Click one to see only its cases.
  3. The test cases, grouped by suite, with their status, priority, last change and assignee.
  4. Run starts a test run with the cases you selected.
  5. New test case adds a case. Press C to do the same. The arrow next to it creates a project or a suite.
  • A test project holds everything for one product or team, and decides who can see it.
  • A test suite is a folder of test cases. Suites can be nested: Downloads sits inside Offline maps.
  • A test case describes one check. Its status tracks the review of the case itself: Draft, Ready for review, Need to fix review comments, Approved or Rejected.
  • A test plan is a reusable list of cases, each with the person who usually runs it.
  • A test run is one round of testing, such as a build before release. It holds a result for each case: Untested, Passed, Failed or Blocked.

When a test fails, create a Tracker issue from the result so the bug is fixed and linked to the test.