Organise Tests with Test Suites

Why use Test Suites?

As your project grows you'll have dozens or even hundreds of Test Cases. Suites keep them organised by feature, workflow, or functional area — for example:

• Authentication
• Checkout
• User Settings
• Product Search
• Order Management

Every Test Case belongs to exactly one Test Suite. You can run a whole suite in one go, schedule it, and see its results together.

The Test Suites page

Open Test Suites from the sidebar. Two summary cards at the top show Total Suites and Total Tests. The table below lists each suite's name, number of Tests, Status, Tags, who created it, and when.

From here you can:

• Search by name or author, and filter by Status or Tag.
• Create a suite with New Suite.
• Edit a suite's details or delete it from its row.
• Tick one or more suites to Run them together, or delete them in bulk, from the toolbar.

Creating a Test Suite

1. 1
   Click New Suite.
2. 2
   Enter a unique Suite Name, for example Auth Flow Suite.
3. 3
   Add a Description to explain what the suite covers.
4. 4
   Optionally choose Tags.
5. 5
   Choose a Status — Active, Draft, or Archived (see below).
6. 6
   Click Create Suite.

Suite status

Working inside a Test Suite

Click a suite to open it. The page shows its description and a table of its Test Cases, and lets you:

• Create a New Test in the suite.
• Search and filter its tests, and open or edit them.
• Run individual tests or click Run Suite to run everything in it. (Run Suite is disabled until the suite has at least one test.)
• Delete tests you no longer need.

Deleting a Test Suite

Deleting a Test Suite moves it — and all the Test Cases inside it — to the Recycle Bin. It also removes the suite from any schedule that runs it.

Deleted suites stay in the Recycle Bin for 15 days, and can be restored at any time in that period. Restoring a suite brings back the Test Cases that were deleted along with it. A test you deleted separately, earlier, stays in the Recycle Bin and must be restored on its own.

After 15 days the suite and its tests are permanently deleted and can't be recovered.

Organising Test Suites

• Group suites by feature or user journey rather than by individual pages.
• Use descriptive names that make the functionality obvious.
• Use Tags for cross-cutting groupings such as Smoke, Regression, or Critical Path.
• Keep each Test Case focused on a single scenario.

Best practices

• Create one suite per major feature or workflow.
• Keep related tests together and use consistent naming.
• Review and remove suites you no longer use.
• Use Tags to organise tests across multiple suites.

Next steps