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

# Test Suite

> A test suite is a collection of related tests that work together to validate specific functionality. Suites help you organize tests by feature, user journey, environment, or workflow for better maintainability and clearer results. Suites also help you organize by environment: when working with suites, users choose an environment to run against, with All Environments selected by default.

## 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 suits 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 Test Suite Flow

<Steps>
  <Step title="Click any suite name to open the suite 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="To see test dependencies, navigate to the Flow View tab.">
    Flow View displays 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>

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