READY status from the project and sets each result to PENDING. Testers then work through each case, record their result, and the run builds a complete record of what was tested, what passed, and what failed.
Runs are snapshots — once a run is created, the set of enrolled cases does not change. You always have a faithful record of exactly what was tested in that session.
Result values
When you work through a test case in a run, you record one of four results.| Result | Meaning |
|---|---|
PASSED | The case behaved exactly as expected |
FAILED | The case did not behave as expected — the feature has a defect |
BLOCKED | The case could not be executed because of a dependency issue or environment problem |
SKIPPED | The case was intentionally not executed in this run |
Results start as
PENDING. A run moves automatically to IN_PROGRESS as soon as the first result is recorded, and to COMPLETED when no results remain PENDING.How to start a run and record results
Open your Test Project
Navigate to your Space, click Test Management in the sidebar, and open the project you want to run.
Click Start Run
Click the Start Run button. In the dialog, give the run a name — use something descriptive like “Sprint 42 — Regression” or “v2.1 Release candidate”.
Optionally link a Milestone
If you want this run to count toward a release or sprint, select a Milestone from the dropdown. You can also do this later.
Work through each case
In the run view, open each case in sequence. Read the preconditions, follow the steps, and compare the actual result against the expected result.
Run history and snapshots
Every run is stored permanently. Open the Test Runs tab of any project to see the full history. Each run shows:- The run name and date
- The linked milestone (if any)
- A breakdown of results: passed, failed, blocked, skipped, pending
- The overall pass rate