Test Management Concepts

This page defines the core building blocks of Test Management and the project-level settings that control them.

​

Test Suites

A test suite is a folder that groups related test cases together. Suites can be nested to create a hierarchy (e.g., API → Users → GET Endpoints).

• Test cases can live inside a suite or remain unsorted until you assign them
• Suites have a name, description, and optional parent suite
• Drag-and-drop suites to reorder them in the Suites view

​

Test Cases

A test case is a single test scenario with a unique Case ID (e.g., TC-6838). Each test case contains core fields, classification fields, automation fields, and metadata.

​

Core fields

​

Classification fields

​

Automation fields

Automation Status and the three flag fields work together: a case can be Manual and flagged To be automated, or Automated and flagged Is Flaky if the linked automated test fails intermittently. Flags are independent of status; set them as needed.

​

Additional metadata

• Tags - Free-form labels (e.g., api, smoke, regression) for categorization and filtering. Tags appear as badges on the test case Details Sheet and can be used in Bulk Actions to add or remove tags across multiple test cases.
• Custom Fields - Project-specific fields configured in Test Case Settings (text, number, textarea, dropdown, or checkbox)
• Attachments - Files attached to the test case

​

Test Steps

Each test case has ordered steps in one of two formats.

​

Version History

Every change to a test case is tracked as a new version. The Versions tab on the Details Sheet shows:

• A timeline of all versions with who made each change and when
• A diff of what changed in each version (additions in green, removals in red)
• The ability to compare any two versions side-by-side
• The ability to restore a previous version

​

Test Case Settings

Open from the ⚙ Test Case Settings in the Test Cases header. The Test Case Settings page is organized into five tabs.

​

Test Case Fields

Test Case Fields contains two sections: Classification and Automation. Each field shows its available values along with a visibility toggle. Enabled fields appear in the test case properties panel, while disabled fields remain hidden. You can also add, edit, or customize values based on your team’s workflow.

​

Classification

Use classification fields to organize and categorize test cases.

​

Automation

Use automation fields to track the automation state of a test case.

​

Custom Fields

Create project-specific fields that appear on every test case in the Details Sheet sidebar under Custom Fields. Click + Add Field to create a custom field. Set the field name, type, optional description, and whether it is required. For dropdown fields, define the list of selectable options. Drag to reorder custom fields. Deleting a custom field removes it and its values from all test cases.

​

Releases

You can also customize the release types used by your team, such as Sprint, Hotfix, and Patch. See Release Type Settings for details.

​

Manual Runs

You can also customize result statuses, run states, environments, and tags. See Manual Run Settings for details.

​

Sessions

You can also customize session states, session types, and finding result statuses for exploratory testing. See Session Settings for details.