Test Executions
Execute test cases manually, track results step by step, and assign testing work across your team.
Overview
Test Executions bridge test case definitions and actual testing. Create an execution session, select test cases to include, assign to team members, and track pass/fail results at the step level.
Where launches capture automated runs from CI, executions capture the manual side of quality: exploratory passes, release sign-off checklists, and regression sweeps that only a human can do. Both feed the same analytics, so release readiness reflects automated and manual results together in one place.
Populating an Execution
An execution can pull test cases from three sources, and you can mix them freely within one session:
- Collections: reusable, curated sets of cases (for example a release smoke checklist) that you run again and again.
- Suites: pull in an entire suite from your case library when you want full coverage of one area.
- Individual cases: hand-pick specific cases and group them under a name of your choice, useful for one-off verification of a bugfix batch.
Cases keep their full definition inside the execution: steps, expected results, attachments and custom fields, so the tester never has to leave the run to look something up.
Creating Executions
- Give the execution a descriptive name
- Select test cases to include from your case library
- Optionally assign to a specific team member
- Link to a release for release readiness tracking
Status Groups
Executions are organized by status in the sidebar:
Newly created, no tests executed yet.
Testing is underway.
All tests have been executed.
Testing cannot proceed due to a dependency or environment issue.
Execution was abandoned.
Executing Tests
- Open an execution to see the list of test cases
- For each test case, walk through the defined steps
- Mark each step as: Passed, Failed, Blocked, or Skipped
- Add notes or comments for failed steps
- The overall test result is determined by individual step results
User Assignment
- Assign executions to specific team members
- View who is responsible for each execution
- Filter by assignee to see your workload
Linking to Releases
- Connect executions to release milestones
- Execution results contribute to release pass rate calculations
- Learn more about release tracking
Execution Statistics
Pass rate across all tests in the execution.
Tests executed versus total tests in the execution.
Distribution of results across passed, failed, blocked, and skipped.