Test Runs
2 min read
Test Runs are standalone testing sessions inside a project. They are not tied to a release and do not change release progress or release readiness.
Use Test Runs when testing needs structure and traceability, but the work should remain independent from a release.
When To Use Test Runs
Section titled “When To Use Test Runs”Use Test Runs for:
- Ad-hoc validation
- Exploratory testing
- Focused regression
- Sprint checks
- Quick verification after a fix
- Testing that should not affect release metrics
Use Release Executions when the work belongs to a release or milestone.
Test Runs Page
Section titled “Test Runs Page”The Test Runs page helps users review standalone testing work.
The table can show:
- Title
- Description
- Project when viewing test runs across a workspace
- Execution Status
- Created On
- Actions
Users can search by title or description, filter by execution status, filter by creation date, filter by project in workspace views, filter by supported custom fields, sort supported columns, adjust visible columns, open details, and open analysis.
Project And Workspace Views
Section titled “Project And Workspace Views”In a project, the Test Runs page shows test runs for the selected project. Users with access can create new test runs from this page.
In a workspace-level view, users can review test runs across projects they can access. The table can include a Project column and a project filter.
Test Run Details
Section titled “Test Run Details”Open a test run details view to review the selected test cases, sources, progress, and editable details.
Users with access can update:
- Title
- Description
- Custom fields
- Manual test case selection
- Selected requirements
- Selected test suites
For detailed editing behavior, see Managing Executions and Test Runs.
Running And Analysis
Section titled “Running And Analysis”After a test run is created, users can run test cases and record results.
Test run results use:
- Passed
- Failed
- Blocked
- Skipped
- Not Executed
Use Running Tests for the testing workflow and Execution Analysis to review progress, ownership, hotspots, and defect signals.
What Test Runs Do Not Do
Section titled “What Test Runs Do Not Do”Test Runs do not:
- Belong to a release.
- Change release progress.
- Change release readiness.
- Group multiple release cycles under one milestone.
For release-based testing cycles, use Release Executions.
Related Guides
Section titled “Related Guides”- Learn how to Create Executions and Test Runs
- Learn how to Manage Executions and Test Runs
- Learn how to Delete Executions and Test Runs
- Review Running Tests
- Review Execution Analysis
- Review Defect Insights