Test Runs
Test runs are where testing moves from planning to execution. A run is a snapshot of test cases that your team works through one by one, recording a result for each. Runs are grouped by cycles, tracked by lifecycle states, and monitored through progress bars, activity timelines, and issue dashboards.
Think of it as race day
Test cases are the training plan — they define what needs to happen. A test run is race day — the moment the plan is put into action. Creating a run is the starting line: you pick which athletes (test cases) compete, assign a race series (cycle), and set course conditions (environment). Each result recorded is a checkpoint crossed. Closing the run is the finish line. The Activity tab is the race commentary, and the Overview tab is the scoreboard.
The list layout
The TEST RUNS tab inside a project is a single-pane workspace with a borderless toolbar and a cycle-grouped run list.
- Toolbar
- Search by title, open the Linear-style filter fly-out (lifecycle state, environment, tags, contributors), switch between table and cards layout, and click New run to create a run. Active filters appear as removable chips below the toolbar.
- Grouped list
- Runs are grouped under their assigned cycle (or No cycle). Each row or card shows the run id (
TR-…), title, lifecycle state, a segmented progress bar, contributor avatars, and a row menu. Click a row to open the run detail page. Multi-select rows to bulk-delete.
How the pieces fit together
Test runs draw on several admin entities you configure elsewhere. The table below shows how each piece is used inside the Test Runs module.
| Admin entity | How it is used in Test Runs |
|---|---|
| Cycles | Organise runs into sprints, releases, or iterations. Runs are grouped under their assigned cycle in the run list. See Cycles. |
| Lifecycle States | Track a run's progress — e.g. Planned, In Progress, Closed. The All/Active/Closed scope tabs switch between views. See Lifecycles. |
| Environments | Attach a platform/browser combination to a run — e.g. Chrome on Windows. See Environments. |
| Statuses | Record individual test outcomes — Passed, Failed, Blocked, Skipped, etc. Statuses power the progress bars and the status grid on the detail page. See Statuses. |
| Tags | Label runs for filtering and categorisation — e.g. Regression, Smoke, API. See Tags. |
| Templates | Control which fields appear for test cases and which fields are available when recording results. See Templates. |
| External References | Link test results to Jira, GitHub, or Azure DevOps issues for traceability. See External References. |
Getting started
- Open a project and click the TEST RUNS tab.
- Browse existing runs in the table, or click New run to create one — this takes you to the test case repository in compose mode.
- Tick the test cases you want in the run, name it, and click Create run.
- Execute tests: open a run, switch to the Cases tab, and tap an inline result button to record an outcome instantly.
- Track progress on the run detail page — Overview summarises health and workload, Cases is the execution workspace, and Activity shows a day-grouped feed.
- Close the run when testing is complete.
Permissions
Access to test run features is controlled by role-based permissions assigned in Roles.
| Permission | What it allows |
|---|---|
| View test runs | See the TEST RUNS tab, browse the run list, and open run detail pages. |
| Create test runs | Create new runs, edit existing run metadata (title, cycle, state, environment, tags, notes, case selection), and close or reopen a run. |
| Execute tests | Record test results and assign test cases to team members. |
| Delete test runs | Permanently delete a run and all its recorded results. |
All action permissions require View test runs implicitly. A user cannot create, execute, or delete runs unless they can also view them.
Common permission combinations
| Goal | Permissions needed |
|---|---|
| Browse runs and view results (read-only) | View test runs |
| Create and configure runs, but not execute | View test runs + Create test runs |
| Execute tests and record results | View test runs + Execute tests |
| Close or reopen a run | View test runs + Create test runs |
| Full test run management | View test runs + Create test runs + Execute tests + Delete test runs |
Browsing & Filtering
Search, filter, and group runs by cycle, state, environment, tags, and more.
Creating a Run
Set up a new run with metadata, notes, and test case selection.
Assigning Testers
Hand cases in a run to a tester — folder tree, filters, match modes, and assign or unassign.
Run Detail
Navigate the v2 detail page with Overview, Cases, and Activity tabs plus an About card for inline edits.
Recording Results
Record test outcomes step by step — statuses, comments, attachments, per-execution result fields, and linked issues.
Managing Runs
Edit, assign, close, and delete runs.