Creating & Managing Test Runs - Step Guide
Test Runs are standalone execution sessions used to run test cases and record results outside of releases. This guide walks through creating, editing, and managing test runs throughout their lifecycle.
Creating Test Runs
To create a new test run:
- Click the Create Test Run button in the header
- Fill in the test run details:
- Click Create to create the test run
Test Run Details
Title
A concise, descriptive name for the test run (required).
Description
A brief summary describing the purpose of the test run (optional).
Custom Fields
If your project has custom fields configured for test runs, they will appear here. Fill them in as required.
Test Case Selection
Test cases can be added using one or more of the following methods.
Manual Selection
- Click Add / Update Test Cases
- Browse or search for test cases
- Select the test cases to include
- Click Add
Manually selected test cases are always included in the test run unless explicitly removed.
From Requirements
- Click Add Requirement
- Select a requirement from the selector
- Test cases linked to the requirement are displayed
- Click Add to include them
Test cases are included based on requirement linkage, not copied.
From Test Suites
- Click Add Test Suite
- Select one or more test suites
- All test cases from the selected suites are included automatically
Test cases are included based on suite membership at the time of creation.
Note:
- You can combine Manual, Requirement, and Test Suite sources
- Test cases are automatically deduplicated
- Removing a source does not remove test cases added via other sources
Understanding Test Case Sources
Each test case in a test run displays source indicators to provide traceability.
- Manual — Explicitly selected by the user
- Requirement — Included via a linked requirement
- Test Suite — Included via a selected test suite
A test case may have multiple source badges if it originates from more than one source.
This helps you understand why a test case is present without duplicating it.
Editing Test Runs
To edit a test run:
- Click the Actions menu (⋮) on the test run
- Select View Details
- Click Edit
- Update:
- Title
- Description
- Custom fields
- Test case sources (add or remove)
- Click Save
Important Editing Rules
- Editing a test run does not modify:
- Previously recorded test results
- Test case execution history
- New test cases added after execution begins start as Not Executed
- Removed test cases lose their execution context permanently
Deleting Test Runs
- Click the Actions menu (⋮) on the test run
- Select Delete
- Confirm deletion in the confirmation modal
When to Use Test Runs
Test Runs are best suited for:
- Ad-hoc testing
- Exploratory sessions
- Regression checks
- Validation after fixes
- Testing outside release milestones
For version-based or milestone-driven testing, use Executions inside Releases instead.
Next Steps
- Learn how to Execute Test Cases
- Understand Best Practices for Test Runs
- Compare with Executions in Releases