Test Cases
A test case is the building block of Test Management. It describes one thing to verify: the action to take, the conditions it requires, and the result you expect. Every test case belongs to a Test Project and optionally to a Test Suite within that project.Test case fields
| Field | Required | Description |
|---|---|---|
| Title | Yes | Short, action-oriented description. E.g. “User can log in with valid credentials” |
| Type | Yes | MANUAL, AUTOMATED, or EXPLORATORY |
| Status | — | DRAFT (default) or READY. Only READY cases are enrolled in runs. |
| Priority | Yes | LOW, MEDIUM, HIGH, or CRITICAL |
| Description | No | Rich-text body — use it for preconditions, steps, and expected results |
| Suite | No | The test suite this case belongs to |
| Automated reference | No | Link to a test file, CI job, or external reference for AUTOMATED type cases |
Writing good test cases
Structure your description with three sections:Status lifecycle
- DRAFT — the case is still being written or reviewed. Excluded from runs.
- READY — reviewed and approved. Included in the next run automatically.
- DEPRECATED — retired case. Excluded from runs but preserved for history.
Creating test cases
Cloning cases
Duplicate an existing case to create a variation: right-click the case in the list → Clone. The clone is created as DRAFT so it can be reviewed before being activated.Importing cases
Bulk-import test cases from CSV: Project → Settings → Import → Upload CSV. Required columns:title, type, priority. Optional: description, suite.
