Creating a Run
A run is composed where the cases are. New run takes you to the test case repository in compose mode, where you tick the cases you want and name the run in a band across the top.
There is no Create Run modal
Runs used to be created from a modal in the Test Runs module, with an Include All Cases toggle and a separate case-picker. That is gone. A run is now built from the cases you are looking at, using the repository’s own folders, filters, search, and saved views — so you never have to rebuild a filter you already had.
The composer opens on the repository at ?compose=fixed, with a band pinned across the top of the list and a selection bar along the bottom.
Step by step
- Click New run in the Test Runs toolbar. You land on the test case repository with the compose band open and the run name focused.
- Type a run name, or leave it blank — see Naming below.
- Optionally pick a Cycle, an Env, a State and Tags from the pills beside the name.
- Tick the cases you want in the list below. Use folders, filters, search, and saved views to narrow it down first.
- To take everything matching your current filter, use Tick all N in the bottom bar. The server resolves that set, so it is not limited to the rows currently loaded on screen.
- Missing a case? New case stays live while you compose — see Writing a case without leaving the composer.
- Click Create run in the bottom bar, or press Enter from the name field.
Writing a case without leaving the composer
If you notice a gap while picking cases, you do not have to abandon the run and start again. The composer is the test case repository, so its New case button keeps working mid-compose (it needs the Create test cases permission, like anywhere else). Write the case in the panel and save it, and:
- It lands in the list already ticked, so it is part of the run you are composing — you do not have to go and find it.
- The tick appears the moment you save, before the server has finished; if the save fails, the case and its tick are both rolled back together.
- Create run is briefly unavailable while a brand-new case is still saving — one round trip — so a run can never be created naming a case the server has not stored yet.
The same applies when you edit an existing run with Edit run… — it opens the same composer.
Esc from the name field cancels the composer. When you are creating a run, Cancel returns you to wherever you came from — the button is labelled with that origin, for example Back to Test Runs. When you are editing a run, the button reads Cancel and throws your edits away.
What the composer asks for
The band is deliberately short. There are five decisions:
| Control | Required | Description |
|---|---|---|
| Run name | No | The run’s title. Leave it blank and the suggestion shown as placeholder is stored instead — the name is never what blocks you from creating a run. |
| Cycle | No | Groups the run under a sprint, release, or iteration. Defaults to No cycle. See Cycles. |
| Env | No | The platform combination under test. Defaults to No environment. The picker offers only environments that are enabled and available to this project — a disabled one is not on the list. See Environments. |
| State | No | The run’s workflow state. Until you pick one, the pill shows the state a new run gets — the test run workflow’s default — and the run starts there. Every run state is offered, including the one the When run is closed rule moves runs to: picking it changes the label and does not close the run. Only Close run… closes a run. See Workflow States. |
| Tags | No | Any number of run tags, picked from a list that stays open while you pick. Defaults to No tags. The list holds the tags your admin set up for runs; with none yet it says so and points to Admin › Tags. See Tags. |
There is no run type to choose: every run keeps the exact cases you tick.
Notes are not set at creation. They are not part of the composer — add them on the run’s Notes card afterwards. See Managing Runs.
Naming
The name field shows a suggestion as its placeholder, built from what you are composing from:
- Composing from a narrower scope such as a folder gives <that scope> — <cycle>, or <that scope> — run when no cycle is set.
- With a cycle picked and no narrower scope: Regression — <cycle>.
- With neither: New test run.
Creating with the field left blank stores that suggestion as the run’s real title.
Choosing the cases
Membership is the tick list — there is no “all cases” toggle. The band tells you what you are about to create, for example A frozen snapshot of the 128 ticked cases, and says so when some ticked cases are filtered out of the current view but still included.
You do not always start from nothing. If an admin has set Include cases in these states on the test case workflow, a new run’s composer opens with every case in those states already ticked, and the band says “N cases included by the Test case workflow — add or remove any”. Those ticks are a starting point: add cases, remove them, or clear the lot. The moment you change the selection the band goes back to counting ticks. With no such setting the composer opens empty, as it always has. Only new runs are seeded — Edit run… opens against the run’s own cases. See Workflow Automation.
Tick all N escalates your current filter into a server-resolved selection. It is unavailable for a few filters the run selector cannot express — the button names them, and you tick the rows you want instead.
Board is unavailable while you choose cases. Ticking needs List or Table, so the Display popover’s Board option is disabled, with the reason Board isn’t available while choosing cases for a run. If you were on Board when you started, the list switches to List and goes back to Board when you leave the composer.
A run cannot exceed 5,000 cases, and a run with no cases cannot be created. Create run stays disabled in both cases.
Other ways in
- Plan a run in this cycle on a cycle detail page opens the same composer with that cycle already selected.
- Edit run… in an open run’s breadcrumb menu reopens the composer against that run, so you can change its name, cycle, environment, tags, and which cases it contains. See Managing Runs.
What happens on create
The run appears immediately — the row is written to the list before the server answers, so there is no spinner. You land on the Test Runs list with the new run in it, not on the run’s detail page.
Snapshot at creation time. A run captures the ticked cases as they exist at that moment. Adding, editing, or deleting cases in the repository afterwards does not change an existing run. To change which cases a run contains, use Edit run… from the run’s breadcrumb menu.
Removing a case from a run keeps its results. When you edit a run and untick cases that already have recorded results, an amber note under the pills says so — for example 6 removed cases have results. They’re kept, and come back if you add the case again. It never blocks Save changes. Hover or focus the count to see the first five of those cases with their last result, and how many more there are. Click it to filter the list to exactly those cases, shown as a Removed with results chip you can clear; tick one again to put it back in the run.