Test Runs are standalone execution sessions used to run test cases and record their results outside the context of a release. They are ideal for ad-hoc testing, exploratory runs, regression checks, and validation tasks that are not tied to a specific release milestone.
Test Runs help teams execute tests flexibly while still tracking progress, assignments, and results in a structured way.
Test Runs are independent containers for executing test cases and recording their outcomes. They provide:
Important:
Test Runs are not linked to Releases.
If you want executions tied to a specific version or milestone, use Executions inside Releases instead.
Within a test run, each test case can have one of the following statuses:
These statuses update the overall progress and analytics of the test run.
The Test Runs page displays all standalone test runs created within the project.
Note:
Test Runs exist only at the project level and are not grouped under Releases.
The test runs table provides a quick overview of each run and displays:
The status column includes:
executed / total test cases (e.g., 15 / 20)This gives an at-a-glance view of execution health and progress.
Use Test Runs when you need:
For version-based or milestone-driven testing, use Releases with Executions instead.
| Feature | Test Runs | Release Executions |
|---|---|---|
| Linked to Release | ❌ No | ✅ Yes |
| Standalone | ✅ Yes | ❌ No |
| Version Tracking | ❌ No | ✅ Yes |
| Multiple Executions per Version | ❌ No | ✅ Yes |
| Best for Ad-hoc Testing | ✅ Yes | ❌ No |