Skip to main content
A test case represents one functional check or validation in your system. It defines what to test, how to test it, and the expected result. Each test case includes metadata for classification, test steps for execution, and automation flags for tracking readiness. Test Case Structure

Quick Reference

Core Fields

Classification

Automation Fields

Pre/Post-conditions

Test Steps

Test cases support one or more steps. Switch between Classic and Gherkin (BDD) formats using tabs in the step editor.
Classic steps use three fields per step:Click Add Step to append additional steps.

Tags

Add keyword tags (e.g., smoke, regression, login) for cross-suite categorization. Tags are comma-separated and can be applied during creation, editing, or bulk operations.

Custom Fields

Create project-specific fields beyond the built-in set. Custom fields appear alongside standard fields in the creation form and editing sheet.

Custom Field Limits

NoteManage custom fields in Project Settings. Unmapped columns during CSV import are automatically created as custom fields.

Attachments

Attach screenshots, documents, or test data files to any test case. Attachments provide additional context for manual test execution or review.
NoteAttachments can be enabled or disabled at the project level in Project Settings.

Version History

Track all changes made to a test case over time. Version history records who changed what and when, providing a full audit trail.
NoteVersion history can be enabled or disabled at the project level in Project Settings.

Metadata

Creating & Editing

Create test cases using forms, quick entry, or suite menus

Organizing at Scale

Suites, tags, and bulk operations

Import & Export

Bulk import from CSV or TestRail

Project Settings

Configure custom fields, attachments, and version history