# Organise Tests with Test Suites

:::lead
A Test Suite is a collection of related Test Cases. It helps you organise your automated tests into logical groups, making them easier to manage, run, and maintain.
:::

## 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](/docs/running-and-results/schedules) 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.

![Test Suites Overview](/images/building-tests/test-suites/test-suites-overview.png)

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. Click **New Suite**.
2. Enter a unique **Suite Name**, for example `Auth Flow Suite`.
3. Add a **Description** to explain what the suite covers.
4. Optionally choose [Tags](/docs/data/tags).
5. Choose a **Status** — **Active**, **Draft**, or **Archived** (see below).
6. Click **Create Suite**.

![Create Test Suite](/images/building-tests/test-suites/create-test-suite.png)

:::info
Suite names must be unique within a project, including suites that are in the [Recycle Bin](/docs/workspace/recycle-bin).
:::

## Suite status

| Status | Meaning |
| --- | --- |
| **Active** | Ready for regular use. |
| **Draft** | Still being built. A draft suite can't run against a **Production** environment. |
| **Archived** | Kept for reference. An archived suite can't be run, and schedules that only target it pause automatically. |

## 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.

![Working inside a Test Suite](/images/building-tests/test-suites/test-suite-details.png)

## Deleting a Test Suite

Deleting a Test Suite moves it — and all the Test Cases inside it — to the [Recycle Bin](/docs/workspace/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.

:::warning{title="Permanent deletion"}
Once an item has been in the Recycle Bin for more than **15 days**, or you delete it forever from there, it 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](/docs/data/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

::::cardgrid
:::card{title="Test Cases" href="/docs/building-tests/test-cases"}
Create and manage the automated tests inside your Test Suites.
:::

:::card{title="Flows" href="/docs/building-tests/flows"}
Reuse common workflows across multiple Test Cases.
:::

:::card{title="Scheduling Runs" href="/docs/running-and-results/schedules"}
Run your suites automatically.
:::
::::