Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.testdino.com/llms.txt

Use this file to discover all available pages before exploring further.

What you’ll learn
  • How to create and edit a test case
  • How to search, sort, and filter the flat list
  • How to configure which badges display on each row
  • What lives on the Details Sheet: content, attachments, link automation, properties, and activity
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. Test Cases list view showing search bar, test case rows, and Details Sheet with properties sidebar

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 four sections.

Classification

FieldDescription
Test SuiteSuite the case belongs to (defaults to the suite selected in the sidebar)
PriorityPriority dropdown (Critical, High, Medium, Low, Not Set)
TypeType dropdown (Smoke, Regression, Functional, Other, etc.)
AutomationAutomation status (Manual, Automated, To Be Automated)

Steps

Switch between Classic and Gherkin with the tabs above Step 1.
FormatStep fields
ClassicAction (what to perform), Test Data (optional), Expected Result
GherkinKeyword (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 To Be Automated, Is Flaky, and Is Muted. Use the search bar at the top to find test cases by title. Results update as you type.

Sort and Filter

Click the Options button to access sort and filter controls.
OptionDescription
Sort byCase ID (default), Last Updated, or Title
DirectionAscending (1→9) or Descending (9→1)
StatusFilter by Active, Draft, or Deprecated
PriorityFilter by Critical, High, Medium, or Low
AutomationFilter by Manual, Automated, or To Be Automated
Active filters are indicated by a badge count on the Options button. Options dropdown showing sort, direction, filter controls, and list options with active filter badge

Clear Filters

Click Clear all at the bottom of the Options dropdown to reset all filters and sorting to defaults.

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. Test case detail page header showing suite breadcrumb, case ID, pagination, print, close, and status badge next to the title

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. Attachments section showing uploaded files with drag-and-drop upload area

Linked Tests

View automated Playwright tests linked to the manual test case with execution details like 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.
  • Link tests using search by name or spec file and filters like All, Linked, or Unlinked.
Link Automated Test dialog showing search bar, All Linked Unlinked tabs with counts, list of automated tests with checkboxes, an N selected badge, and a Link test button

Properties

The Properties section shows Status, Priority, Suite, Tags, and Automation status by default. Click More properties to reveal two more groups:
  • Basic - Type, Severity, Reporter, Created, Updated
  • Advanced - Layer, Behavior, Flags
Each value is editable via its dropdown. Any project-specific custom fields from Test Case Settings appear here too. Properties section showing Status, Priority, Suite, Tags, Automation status, and a More properties toggle that reveals Basic and Advanced field groups

Activity

Four tabs at the bottom of the page.
TabWhat It Shows
CommentsDiscussion thread on the case
HistoryVersioned snapshots with who made each change, when, and a side-by-side diff. Click Restore to revert to a previous version.
ResultsManual run results that include this case, with status and the run that produced each result
IssuesLinked issues (Jira, Linear, etc.) referenced from this 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. Details Sheet header showing print icon in the top-right corner Print preview showing test case PDF with all fields and test steps
TipUse 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