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 Status tab is the scoreboard.
The two-panel layout
The TEST RUNS tab inside a project uses a split-pane design.
- Left panel — Cycle tree
- A hierarchical tree of your project's cycles. Click a cycle to filter the run table to only runs assigned to that cycle. Three built-in groups appear at the top: All (every run), Assigned (runs linked to any cycle), and Unassigned (runs with no cycle). Each node shows a badge with the number of runs it contains. The panel is resizable and can be collapsed to a narrow icon strip.
- Right panel — Run table
- A filterable, searchable data table listing all runs matching the current filters. Each row shows the run title, its cycle, lifecycle state badge, a progress bar with completion and pass/fail counts, contributor avatars, and an actions menu. Click a row to open the run detail page.
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. The cycle tree groups runs in the left panel. See Cycles. |
| Lifecycle States | Track a run's progress — e.g. Planned, In Progress, Closed. The lifecycle toggle switches between Active and Closed 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.
- Choose which test cases to include — all cases or a filtered subset.
- Execute tests: open a run, click a case in the results table, and click Add Result to record an outcome.
- Track progress on the run detail page — the Status tab shows completion rates, the Activity tab shows a day-by-day timeline, and the Issues tab aggregates linked defects.
- 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 and edit existing run metadata (title, cycle, state, environment, tags, notes, case selection). |
| Execute tests | Record test results, assign test cases to team members, and close runs. |
| 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 close runs | View test runs + Execute tests |
| 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.
Selecting Test Cases
Master the case selection modal — folders, filters, match modes, and selection patterns.
Run Detail
Navigate the three-pane detail page with Results, Status, Activity, and Issues tabs.
Recording Results
Record test outcomes step by step — statuses, comments, attachments, and linked issues.
Managing Runs
Edit, assign, close, and delete runs.