> ## 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](/managing-tests/folders) to keep related suites grouped by product area, team, or domain.

<Note>
  **Important**: All tests must be added to a Test Suite.
</Note>

<Frame caption="Test Suites overview displaying suite names, last run times, number of tests, and latest results">
  <img src="https://mintcdn.com/spur/nkJAnk4T86p0gJmp/Image2026-02-10at11.20AM.jpeg?fit=max&auto=format&n=nkJAnk4T86p0gJmp&q=85&s=76a63817e8dedf99c4e614fdfda028bb" alt="Screenshot 2026 02 05 At 3 51 37 PM" width="3026" height="1634" data-path="Image2026-02-10at11.20AM.jpeg" />
</Frame>

## View a test suite's flow

<Steps>
  <Step title="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.

    <Frame>
      <img src="https://mintcdn.com/spur/nkJAnk4T86p0gJmp/Image2026-02-10at11.25AM.jpeg?fit=max&auto=format&n=nkJAnk4T86p0gJmp&q=85&s=d062431ef14c70170cf0393c1dfcfffd" alt="Screenshot2026 01 29at5 04 10AM" width="3026" height="920" data-path="Image2026-02-10at11.25AM.jpeg" />
    </Frame>
  </Step>

  <Step title="View test dependencies">
    Navigate to the **Flow View** tab to see a visual representation of how tests execute in sequence, showing parent-child relationships where child tests only run if their parent passes. Learn more about [Flow View and Test Dependencies](/authoring-tests/dependencies).

    <Frame>
      <img src="https://mintcdn.com/spur/nkJAnk4T86p0gJmp/Image2026-02-10at11.24AM.jpeg?fit=max&auto=format&n=nkJAnk4T86p0gJmp&q=85&s=9d174395825635416624208f30f768a1" alt="Screenshot2026 01 29at5 06 35AM" title="Screenshot2026 01 29at5 06 35AM" className="mx-auto" width="3026" height="1750" data-path="Image2026-02-10at11.24AM.jpeg" />
    </Frame>
  </Step>
</Steps>

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

<Note>
  Test suites maintain the integrity of your testing workflow by executing tests in the correct sequence, ensuring each step builds upon the previous ones.
</Note>

<Tip>
  Keep your test suites focused and organized around specific features or user journeys for better maintainability and clearer results.
</Tip>

## 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](/authoring-tests/environments/environments) 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](/authoring-tests/scenarios/scenario-tables) 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](/authoring-tests/environments/environments), [Scenario Tables](/authoring-tests/scenarios/scenario-tables), and [Test Plans](/managing-tests/test-plans/test-plans).

## 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, it's recommended to keep them focused on specific features or workflows to maintain clarity and ease of maintenance.
</Warning>


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