Selecting Test Cases
The case selection modal lets you build precise test case sets using folder navigation, multi-criteria filters, and match modes. It opens from the Create Run or Edit Run modal whenever you need granular control over which cases are included.
Think of it as assembling a team roster
The folder tree is your squad list — click a squad to include all its members. Filters are your selection criteria — fitness tests, skill ratings, certifications. Match mode decides whether an athlete must pass every criterion (Match All) or just one (Match Any). The summary count at the bottom is your final roster size.
Opening the modal
- In the Create Run or Edit Run modal, make sure the Include All Cases toggle is off.
- Click the case selection button.
- The modal opens with a folder tree on the left and filter controls on the right.
Folder tree
The left side of the modal displays the project’s folder hierarchy.
- Click a folder to include all cases inside it.
- When you select a parent folder, its descendants (sub-folders) are included automatically.
- You can select multiple folders — folder selection uses OR logic (cases in any selected folder are included).
- Each folder node shows a badge with the number of cases it contains.
Filters
The right side of the modal provides multi-criteria filters. Each filter narrows the selection to cases matching the chosen values.
| Filter | What it matches |
|---|---|
| Templates | Cases created with the selected templates. |
| Lifecycle States | Cases in the selected repository lifecycle states (e.g. Active, Draft). |
| Statuses | Cases whose most recent result has the selected status (e.g. Passed, Failed). Useful for re-testing failed cases. |
| Tags | Cases tagged with any of the selected tags. |
| Environments | Cases associated with the selected environments. |
| Custom Field Values | Cases where a specific template field matches a given value. Add multiple field filters for precise targeting. |
Match mode
A toggle at the top of the filter area controls how multiple filters combine.
| Mode | Behaviour |
|---|---|
| Match All (AND) | A case must satisfy every active filter to be included. Use this for precise, narrow selections. |
| Match Any (OR) | A case is included if it satisfies at least one active filter. Use this for broader, inclusive selections. |
Match mode applies to filters only. Folder selection always uses OR logic — cases in any selected folder are included regardless of match mode. Filters then narrow down within those folders.
Summary counts
The modal footer shows a live count of how many cases match the current selection. The count updates in real time as you check folders, add filters, or change the match mode.
Selection patterns
Here are common scenarios and how to configure them:
Full regression
Enable the Include All Cases toggle in the run modal. You do not need to open the selection modal at all.
Smoke test subset
Open the selection modal, select the “Smoke Tests” folder in the tree, and leave all filters empty. Only cases in that folder (and its sub-folders) are included.
Re-test failed cases
Open the selection modal, leave folders unselected (or select the relevant folder), add a Statuses filter set to “Failed”, and set match mode to Match All. This selects only cases whose last result was Failed.
Cross-template tagged selection
Open the selection modal, set Templates to “API Tests” and “UI Tests”, set Tags to “P1”, and set match mode to Match All. This selects cases that use either template AND are tagged P1.
Confirming the selection
Click Confirm to apply the selection and return to the run modal. The form displays the total case count. To adjust, reopen the modal — your previous selections are preserved.
Selection is evaluated at creation time. The case set is resolved and snapshotted when you save the run. Cases added to the repository after the run is created are not included automatically. Edit the run to update the selection.