Skip to main content
A test suite is the fundamental unit of testing in Spur, representing a collection of related tests that work together to validate specific functionality. This page will guide you through managing and running your test suites.

Test Suite Page: listing all the test suites in your application.

​
Test Suite Flow View

Flow View: Visual representation of test dependencies.

​
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 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
Instead of creating separate test suites for dev, staging, and production, create one suite and run it across all environments. This ensures consistency and reduces maintenance.
Learn more about Environments and Test Plans.

​
Best Practices

  1. Logical Grouping: Group related tests together in a suite
  2. Clear Dependencies: Establish clear relationships between tests
  3. Maintainable Size: Keep suites focused and manageable
  4. Regular Execution: Run suites frequently to catch issues early
  5. 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.