Test cases, suites and the Step Library

Test suites

Test Suites is a folder tree for your test cases, for example Authentication → Login & OAuth. Select a folder to see its cases (including those in sub-folders). Open a suite in grid view to edit many cases quickly, like a spreadsheet.

Writing a test case

A test case has:

• Title and optional objective, preconditions and postconditions
• Steps, each with an action and an expected result
• Priority (low, medium, high, critical) and type (functional, regression, edge case, negative…)
• Status: draft, approved, stale (approved and run before, but not within the project's stale-detection window, set in Project settings → Stale detection) or deprecated
• Optional custom fields, if your admin has set them up

Open any case to edit it in the side drawer. Its tabs show properties, run history, change history, linked bugs, comments and automation.

Approval

Only approved (and stale) cases are included in test runs, and only they count toward coverage and readiness. Running a stale case again marks it approved. When a requirement's text changes, the requirement shows a banner so you can review its test cases.

Step Library

Some step sequences appear everywhere ("Log in as admin", "Add an item to the cart"). Save them once in the Step Library, then insert them into any test case. Updating a shared step updates every case that uses it.

History and comments

Every change to a test case is recorded, with who made it and when, in its History tab, whether it was made in the editor, by bulk edit, by approval, a review or the agent. Each entry keeps the version before the change: choose Restore the version before this change to put back the title, objective, preconditions, priority, type, notes and steps (status and links stay as they are). A restore is recorded too, so you can undo it the same way. Use Comments to discuss a case with your team.

Automation

Automated results from CI are linked to test cases by matching the test's title or the case's automation key. The most reliable way is to put the case's number in the test title, for example [TC-42] user can log in. See CI integration.