Skip to main content
A test case describes one thing to verify, with ordered steps and the expected result for each. You keep cases in folders and find them by title or key.

Create a case

1

Open the Cases tab

Choose New test case. The folder you have open is preselected.
2

Fill in the case

Give it a title, a priority (low, medium, high or critical) and a type (manual, automated or exploratory). Add preconditions, test data and an estimate if they help the tester.
3

Add steps

Each step has an action and an expected result. You can reorder steps with the arrows.
4

Save

The case gets a key such as QA-T12 and starts as a draft.

Versions and review

Every change to a case is a new version. A version is in one of these states: You submit a draft for review, and a reviewer approves it or rejects it with a reason. The person who submitted the version gets a message when it is rejected. If the project does not require approval, a saved version is approved at once.
With the four-eyes rule on, the person who last edited a version cannot approve it.
Results belong to the version they were recorded on. Editing a case later never changes what an earlier run proved. The Versions panel shows what differs between two versions, field by field and step by step.

Folders

Folders nest to any depth and have no effect on execution. Drag a case or a folder to move it. A folder that still holds subfolders cannot be deleted. Link a case to the work items or requirements it covers. When the linked item changes after the case was last reviewed, the link is marked suspect until someone confirms it is still valid. Suspect links show up in the reports.

Archive and delete

A case that was never executed can be deleted. A case with executions can only be archived, so its history stays complete. Archived cases can be restored.
Last modified on October 24, 2026