Skip to main content

​
Test Runs

A test run is an execution session. When you start a run, Collabase automatically enrolls every test case with READY status and sets each result to PENDING. Testers work through each case, record their result, and the run builds a complete record of what was tested. Runs are immutable snapshots — once created, the set of enrolled cases doesn’t change, giving you a reliable historical record.

​
Starting a run

  1. Open the Test Project → Runs tab
  2. Click + New Run
  3. Name the run (e.g. “Sprint 14 — Regression”)
  4. Optionally attach a Milestone
  5. Click Create — Collabase enrolls all READY cases immediately

​
Recording results

Open the run to see the full case list with a result picker per case:
ResultMeaning
✅ PASSCase executed and expected result was observed
❌ FAILCase executed and expected result was NOT observed
⛔ BLOCKEDCase could not be executed (environment issue, dependency)
⏭️ SKIPDeliberately excluded from this run
Click the result and optionally add a comment — for FAIL results, describe what happened so developers can reproduce it.

​
Run progress

The run header shows live progress:
  • Pass rate — percentage of PASS results vs. total executed
  • Pending — cases not yet recorded
  • Passed / Failed / Blocked / Skipped — result counts

​
Completing a run

Click Complete Run when all cases have a result (or when you’re done with the session). Completed runs are locked — results can’t be changed. The run’s final pass rate is recorded and fed into milestone metrics. On a FAIL result, click Create Bug to automatically open a new Project task pre-filled with:
  • Title from the test case title
  • Description from the run comment
  • Link back to the test run
This bridges Test Management and Projects with one click.

​
Re-running failed cases

Create a new run specifically for failed cases: New Run → Run failed cases from [previous run]. Collabase copies only the FAIL results from the selected run as the starting case set.