Test Cases

Search, sort, and filter test cases in a flat list, and view full details with tabs for overview, attachments, history, and linked tests.

The Test Cases view shows a flat list of all test cases across all suites. This view is useful when you want to search, sort, or filter without navigating the suite hierarchy.

Create Or Edit Test Case

Click + New in the header to open the New test case slide-over. To edit an existing case, open it from the list and click Edit in the Details Sheet header. The form is split into 4 sections.

Classification

Field	Description
Test Suite	Suite the case belongs to (defaults to the suite selected in the sidebar)
Priority	Priority dropdown (Critical, High, Medium, Low, Not Set)
Type	Type dropdown (Smoke, Regression, Functional, Other, etc.)
Automation	Automation status (Manual, Automated)

Steps

Switch between Classic and Gherkin with the tabs above Step 1.

Format	Step fields
Classic	Action (what to perform), Test Data (optional), Expected Result
Gherkin	Keyword (Given, When, Then, And, But) + text

Click + Add Step to add more steps. Expand Add pre/postconditions to set what must be true before the case runs and the expected system state after.

Tags

Type a tag and press Enter (or click Add) to attach a tag. Tags appear as badges on the case row in the list and in the Details Sheet.

Advanced

Advanced fields are hidden by default. Expand this section to set Severity, Layer, Behavior, and automation flags like Is Flaky and Is Muted.

Search

Use the search bar at the top to find test cases by title. Results update as you type.

Sort and Filter

The toolbar has 3 separate controls: Sort, Filter, and Columns.

Control	What it does
Sort	Sort by Case ID (default), Last Updated, or Title, in ascending or descending order. Reset sort returns to the default.
Filter	Filter by status, priority, automation, and any other field your project defines, including custom fields.
Columns	Choose which columns the list shows.

Applied filters appear as chips above the list. Click Clear all on that row to remove them all at once.

Columns

Click Columns to choose what each row shows. Status and Priority are on by default; Automation, Severity, Type, Layer, Behaviour, and Created by can be turned on.

Columns need room to render, so some appear only on wider screens. The picker tells you which ones: a column ticked on a narrow window shows once there is space for it.

Details Sheet

Click any test case row to open the Details Sheet from the right side. It shows all test case information on a single scrollable page without tabs.

The header includes the suite path, case ID with copy link, pagination controls, print option, close button, and status badge. You can update the test case status directly from the header dropdown.

Description

The Description section gives a brief overview of what the test case is meant to validate, helping users quickly understand its purpose and scope before execution.

Steps

The Steps section defines the test execution flow using Action and Expected Result columns. Users can switch between Classic and Gherkin views and hide or show the Expected Result column using an eye icon.

Steps support images, screenshot-only evidence, and pinned attachments. New steps can be added using the + Add Step button.

Pre-conditions and Post-conditions

This section appears below Steps as a collapsible block, where Pre-conditions define the required setup or system state that must be in place before execution begins, and Post-conditions define the expected system state after execution is completed.

Attachments

Drag-and-drop or browse to upload. A case allows up to 10 attachments total.

Linked Automation Tests

A link connects a test case to the automated Playwright test that covers it. Linking is what makes a case report its result automatically: in a run, a linked case takes its verdict from CI instead of waiting for someone to test it by hand. An unlinked case stays manual and is never reported as an automation gap.

The section lists each linked automated test with its status, run, branch, and date.

• If no tests are linked, a Link automation button appears. Once linked, a + Link button is shown to add more tests.
• Search by test name or spec file, and filter by Linked only, Unlinked only, or Linked + unlinked.
• Each row shows the browsers the test runs on, so you can confirm you picked the right one before linking.

The picker groups tests under the spec file they live in, and names the test case you are linking to at the top so you do not lose track of it mid-search. Each test shows the platform it runs on and its last run, which is how you tell two similarly named tests apart before you commit to one. Use Expand all to open every spec file at once, and the filter to show Unlinked only while you work through a backlog.

To create cases from tests you already automated, open New and choose From automation. It creates the test case and the link together, which avoids a mismatch between the 2.

Keeping Links Accurate

A run and a release are only as correct as the links behind them, so getting the mapping right is not optional. 4 rules decide whether a case reports the right result.

Rule	What it means for you
Link the test once, not once per browser	1 link covers every browser CI runs that test on. Adding a browser to CI needs no re-linking
Moving or renaming a spec file breaks the link	The test’s identity changes with its file path, so the old link can never resolve again. Re-link the case after a refactor
Link the test that proves the case	A link to a loosely related test reports a green CI result for a case nobody validated
Links and automation status stay in step	Setting a case to anything other than Automated removes its links. TestDino asks first, because switching back does not restore them

When a link goes stale, the run shows the case as Not run with No CI match in recent runs. Re-link this case to an automated test. That message means the link is broken, not that the pipeline skipped the test. See why a case shows Not run.

Unlinking the last automated test from a case reverts it to Manual.

Properties

The Properties section shows Status, Priority, Tags, Automation status, Flags, Type, and Severity by default. Click More properties to reveal:

• Layer and Behaviour
• Current Run Status - the case’s result and assignee from the most recent run it was executed in, with a link to that run. Hidden for a case that has never been run.

Each value is editable via its dropdown. Any project-specific custom fields from Test Case Settings appear here too.

Who created and last updated the case is shown at the bottom of the panel, with the date and the person’s name.

Activity

4 tabs at the bottom of the page.

Tab	What It Shows
Comments	Discussion thread on the case
History	Versioned snapshots with who made each change, when, and a side-by-side diff. Click Restore to revert to a previous version.
Results	Manual run results that include this case, with status and the run that produced each result
Issues	Linked issues (Jira, Linear, etc.) referenced from this case

Print Test Case

Click the print icon in the top-right corner of the Details Sheet to generate a printable PDF of the test case. The PDF includes the test case ID, title, suite, all classification fields, automation status, description, pre/post-conditions, and test steps.

Tip

Use Bulk Actions to print multiple test cases at once.

Suites

Browse test cases organized by suite

Bulk Actions

Edit, delete, or print multiple test cases

Concepts & Settings

Field definitions, step formats, and project settings