.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26){kind=logo}
Test Runs
A test run is an execution session. You select which test cases to include, and testers work through each case, perform the described steps, and record a result. When the run is complete, it becomes an immutable quality snapshot for that point in time. Collabase does not run tests for you — it provides the structure for testers to record their observations. For automated cases, results can be submitted via the API from your CI/CD pipeline.Result status values
Each test case in a run receives one of the following result statuses:Creating a test run
1
Open the Test Runs tab
In your test project, click the Test Runs tab in the top navigation.
2
Click + New Run
Click + New Run in the top right corner.
3
Name the run
Enter a descriptive name for this run. Use a name that identifies the scope and date — for example, “Sprint 22 Regression – 2026-06-21” or “v3.0 Release Candidate – Full Smoke”.
4
Select cases or suites to include
By default, all READY cases in the project are included. To limit the run to specific cases or suites, click Select cases and choose which suites or individual cases to include. Cases with DRAFT or DEPRECATED status are never included.
5
Assign a milestone (optional)
If this run belongs to a release or sprint milestone, select it from the Milestone dropdown. The run’s results will contribute to the milestone’s aggregate metrics.
6
Create the run
Click Create Run. The run is created with status PLANNED and all included cases start with result status PENDING.
Executing a test run
1
Open the run
Click the run name in the Test Runs list. The run detail view shows all included cases with their current result status.
2
Start the run
Click Start Run. The run status changes from PLANNED to IN_PROGRESS.
3
Work through each case
Click a case to open its detail. Read the steps and expected results. Perform the described steps in your test environment.
4
Record the result
At the top of the case detail in the run, click the result you observed: Passed, Failed, Blocked, or Skipped.
5
Add a note (recommended for failures)
Click Add note to enter observations. For failed cases, describe exactly what went wrong — this information is visible to developers and helps them reproduce the issue. For blocked cases, describe what prevented execution.
6
Move to the next case
Click Next case or select another case from the list on the left. Continue until all cases have a result.
Run status
Completing a run
When you have recorded results for all cases (or when you want to close the run session), click Complete Run.- The run status changes to COMPLETED.
- All results are locked — they cannot be changed after this point.
- The final pass rate is calculated and stored with the run.
- If the run is linked to a milestone, the milestone’s metrics are updated.
You can complete a run even if some cases are still Pending or Skipped. Pending cases will not count toward the pass rate. Only Passed and Failed cases are used in the rate calculation.
Run metrics
After a run is completed, its metrics panel shows:
Metrics are computed on demand — they are not stored separately. Viewing a run or milestone triggers the calculation.
If a run contains zero Passed and zero Failed results (all cases are Blocked, Skipped, or Pending), the pass rate displays as N/A rather than 0%.