Test Cases

The Test Cases page is the core workspace where your team writes, organises, and maintains every test case in a project. A scope bar tells you which folder you are in, the main surface lists your cases as a list, table, or board, and clicking any row slides open a side panel so you can read and edit a case without losing your place.

Think of it as a library

The easiest way to understand the Test Cases page is to think of it as a library:

  • Folders are the shelves — they organise cases by feature, module, sprint, or any structure you choose.
  • Test cases are the books — each one is a self-contained item with a title, properties, and content.
  • Templates are the book formats — your administrator defines which fields a case carries, so a Regression case and a Smoke case can hold different information.
  • The main surface is the catalogue — a searchable, filterable view of every case in scope.
  • The side panel is pulling a book off the shelf — a quick read and edit. Open a case full page when you also want its attachments, linked issues, comments, history, and execution results.

How the page is laid out

Scope bar
A breadcrumb showing which folder you are browsing, with a jumper for switching folders quickly and a Group by folder toggle. Folder actions live in its menu. There is no separate folder-tree sidebar — the scope bar is the folder navigation. See Folders.
Toolbar
Saved views, search, Filter, Display, the breakdown panel, AI generation, Create run, and New case. Active filters appear as removable chips on the row beneath. See Browsing & Search.
Main surface
Your cases in one of three views — List, Table, or Board — switched from the Display popover or the ⌘K palette. Selecting rows reveals a bulk action bar.
Side panel
Opens when you click a case row, with Steps and Details tabs. Edits save as you leave each field. Use Open full page for the complete case. See Case Detail.

The URL is the view. Your folder, search text, filters, sort, and grouping all live in the address bar, so you can bookmark a view or paste it to a teammate and they will see exactly what you see.

How the pieces fit together

Test cases bring together several admin-configured entities. Each one is set up once by an admin and then used by project members when creating and viewing cases:

Admin entity Where it appears in Test Cases Learn more
Templates Determines which fields a case carries, and in what order Test Case Templates
Test Case Fields The custom inputs on a case (text, steps, dropdowns, etc.). Option-typed fields also become filters, columns, and grouping options. Fields
Lifecycle States The State property and column (e.g. Draft, Ready, Approved), with its configured icon and colour Lifecycles
Statuses The Status (latest) column and the Last result filter — the most recent execution result Statuses
Tags Shown as Labels on a case; also a filter and a bulk action Tags
External References The Linked issues section on a case, and the Linked issues filter External References

Getting started

  1. Open your project and click Test Cases in the sidebar.
  2. Optionally create your first folder to organise cases — for example, Login, Checkout, or API. You can skip this and file cases later: a case created without a folder goes to Unfiled.
  3. Click New case (or press C) to create a test case. Give it a title and press ⌘Enter.
  4. Fill in its steps and fields. There is no Save button — edits commit as you go.
  5. Use search and filters to find cases as your repository grows.
  6. Click any case row to open the side panel, or open it full page for comments, results, and history.

Permissions

Access to test case and folder features is controlled by role-based permissions assigned in Roles.

Permission What it allows
View test cases See the case list and open a case. Also lets you post comments.
Create test cases Create new cases via New case or the C shortcut
Edit test cases Edit an existing case — title, properties, labels, steps, and prose
Bulk edit test cases Change fields, labels, or folder across a multi-case selection. Needs Edit test cases as well.
Delete test cases Delete a single case. Bulk delete additionally requires Bulk edit test cases, so holding delete alone can never destroy a whole selection.
View folders See the folder scope bar and jumper
Manage folders Create, rename, move, and delete folders
View external references See linked issues in the detail panel
Manage external references Link and unlink external issues

Common permission combinations

Workflow Permissions needed
Browse cases, open them, and comment View test cases + View folders
Create a case in a folder Create test cases + View folders
Create a case and link an issue Create test cases + View folders + Manage external references
Edit an existing case Edit test cases
Change a field across many cases at once Edit test cases + Bulk edit test cases
Delete a selection of cases Edit test cases + Bulk edit test cases + Delete test cases
Reorganise folders Manage folders