> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Spur is an AI-powered QA engineer that lets teams create and run automated end-to-end tests for web and mobile apps using natural language.
> When answering questions about Spur, cite the relevant page from docs.spurtest.com.

# Test Suites: Group and Run Related Tests Together

> Group related Spur tests into a test suite to organize by feature, user journey, or environment, then run and manage them together against any target env.

## View test suites

Navigate to **Test Suites** in your Spur Dashboard to see all suites with their environments, test counts, and latest results. You can also organize suites into [Folders](https://docs.spurtest.com/managing-tests/folders.md) to keep related suites grouped by product area, team, or domain.

> [!NOTE]
>
> **Important**: All tests must be added to a test suite.

![Test Suites overview displaying suite names, last run times, number of tests, and latest results](https://mintcdn.com/spur/8SIYEB8X4PSFcROt/images/managing-tests/test-suite/test-suites-overview.jpeg?fit=max\&auto=format\&n=8SIYEB8X4PSFcROt\&q=85\&s=a96d25fb36a4c854cdbe78315b40312a)

Test Suites overview displaying suite names, last run times, number of tests, and latest results

## Move, duplicate, or delete a suite

On the **Test Suites** page, click the three-dot menu (⋯) on a suite's row to manage it:

* **Move Suite**: Opens **Move Test Suites**. Choose a destination folder and click **Move**. See [Folders](https://docs.spurtest.com/managing-tests/folders.md).
* **Duplicate Suite**: Creates a copy of the suite. The copy is named after the original with `(Copy)` added, and you can change the name before you confirm.
* **Delete Suite**: Deletes the suite. To confirm, type `Delete Suite` in the dialog.

The same options are available in the suite's **Settings** menu on its detail page.

## View a test suite's flow

**1. Open the suite detail page**

Click any suite name to open its detail page. By default, you'll see the "All Tests" view showing a list of all tests in the suite.

![All Tests view listing every test in the suite](https://mintcdn.com/spur/8SIYEB8X4PSFcROt/images/managing-tests/test-suite/all-tests-view-suite.jpeg?fit=max\&auto=format\&n=8SIYEB8X4PSFcROt\&q=85\&s=6b7279b4634871c9c3ed7610547c0b64)

**2. View test dependencies**

Open the **Dependencies** tab to see how tests connect. Child tests run after their parent passes. Learn more about [test dependencies](https://docs.spurtest.com/authoring-tests/dependencies.md).

![Screenshot2026 01 29at5 06 35AM](https://mintcdn.com/spur/8SIYEB8X4PSFcROt/images/managing-tests/test-suite/flow-view-test-dependencies.jpeg?fit=max\&auto=format\&n=8SIYEB8X4PSFcROt\&q=85\&s=2bb8759e9c09ea1596789b7e47076258)

## Running test suites

When you run a test suite, Spur executes all tests within the suite in their specified order, respecting dependencies and ensuring proper flow. The execution view provides real-time feedback on:

* Current test status
* Progress through the suite
* Any errors or issues encountered
* Test execution time

> [!TIP]
>
> Keep your test suites focused and organized around specific features or user journeys for better maintainability and clearer results.

## Editing enabled environments

You can restrict which environments a test suite runs against directly from the suite page. Open the suite's **Settings** menu (top-right) and select **Edit Environments**. In the modal, toggle the environments you want the suite to run in and save — every test in the suite is updated in a single action.

Use this to keep a suite scoped to just the environments where it makes sense (for example, disabling Production for a suite that seeds data).

## Running tests across environments

Test suites can be run across **multiple enabled environments** without duplication. Use [Environments](https://docs.spurtest.com/authoring-tests/environments/overview.md) to configure different deployments (Dev, Staging, Production) and run the same test suite in all of them.

**Benefits:**

* No need to duplicate test suites for different environments
* Consistent test logic across all deployments
* Easy comparison of results across environments
* Centralized test maintenance

You can also connect suites to [Scenario Tables](https://docs.spurtest.com/authoring-tests/scenarios/scenario-tables.md) to run the same tests across multiple data-driven flows using parameterized inputs. Each suite can be connected to a single Scenario Table only, ensuring a clear mapping between suite and scenario data.

Learn more about [Environments](https://docs.spurtest.com/authoring-tests/environments/overview.md), [Scenario Tables](https://docs.spurtest.com/authoring-tests/scenarios/scenario-tables.md), and [Test Plans](https://docs.spurtest.com/managing-tests/test-plans/overview.md).

## Best practices

* **Logical grouping**: Group tests that validate the same feature, user journey, or workflow into the same suite, so results stay focused and easy to interpret.
* **Clear run order**: Define a formal execution order for tests in the suite so preconditions run first, core flows run in sequence, and any teardown or cleanup last.
* **Maintainable size**: Keep suites focused and manageable.
* **Clear naming**: Use descriptive names for easy identification.

> [!WARNING]
>
> While test suites can contain many tests, keep them focused on specific features or workflows to maintain clarity and ease of maintenance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.