Skip to main content

​
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 to keep related suites grouped by product area, team, or domain.
Important: All tests must be added to a Test Suite.
Screenshot 2026 02 05 At 3 51 37 PM

​
View Test Suite Flow

1

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.
Screenshot2026 01 29at5 04 10AM
2

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.
Screenshot2026 01 29at5 06 35AM

​
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
Test suites maintain the integrity of your testing workflow by executing tests in the correct sequence, ensuring each step builds upon the previous ones.
Keep your test suites focused and organized around specific features or user journeys for better maintainability and clearer results.

​
Running Tests Across Environments

Test suites can be run across multiple enabled environments without duplication. Use 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 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, Scenario Tables, and 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.
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.