> ## Documentation Index
> Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt
> Use this file to discover all available pages before exploring further.
> A test run is an execution session — select cases to test, record a result for each one, and capture a quality snapshot for that point in time.
# Test runs
# 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:
| Status | Meaning |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pending** | The case has not yet been executed in this run. This is the default status when a run is created. |
| **Passed** | The tester performed the steps and all expected results were observed. |
| **Failed** | The tester performed the steps and at least one expected result was not observed. |
| **Blocked** | The case could not be executed because a prerequisite or dependency was not met (for example, a test environment was unavailable or a prior case failed in a way that makes this one impossible to run). |
| **Skipped** | The case was deliberately excluded from this run session. Skipped cases do not count toward the pass rate. |
## Creating a test run
In your test project, click the **Test Runs** tab in the top navigation.
Click **+ New Run** in the top right corner.
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".
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.
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.
Click **Create Run**. The run is created with status PLANNED and all included cases start with result status PENDING.
## Executing a test run
Click the run name in the Test Runs list. The run detail view shows all included cases with their current result status.
Click **Start Run**. The run status changes from PLANNED to IN\_PROGRESS.
Click a case to open its detail. Read the steps and expected results. Perform the described steps in your test environment.
At the top of the case detail in the run, click the result you observed: **Passed**, **Failed**, **Blocked**, or **Skipped**.
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.
Click **Next case** or select another case from the list on the left. Continue until all cases have a result.
## Run status
| Status | Meaning |
| --------------- | ---------------------------------------------------------------------------------------------- |
| **Planned** | The run has been created but execution has not started. Cases are enrolled and set to Pending. |
| **In Progress** | Execution is underway. Results are being recorded. The run is editable. |
| **Completed** | All cases have a result and the run has been closed. Results are locked and cannot be changed. |
## 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:
| Metric | How it is calculated |
| ------------- | ----------------------------------------------------------------------------------------------- |
| **Pass rate** | Passed ÷ (Passed + Failed) × 100. Blocked and Skipped cases are excluded from this calculation. |
| **Passed** | Count of cases with PASSED result |
| **Failed** | Count of cases with FAILED result |
| **Blocked** | Count of cases with BLOCKED result |
| **Skipped** | Count of cases with SKIPPED result |
| **Pending** | Count of cases still in PENDING status (only in non-completed runs) |
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%.