Skip to main content
A test suite is the fundamental unit of testing in Keystone, 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

Visual Test Dependencies

Flow view provides a visual representation of test dependencies, making it easy to understand test relationships and execution order.

​
Running Test Suites

When you run a test suite, Keystone executes all tests within the suite in their specified order, respecting dependencies and ensuring proper flow.

Current Status

Real-time test status

Progress

Suite completion tracking

Error Detection

Issue identification

Execution Time

Performance metrics
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.

​
Duplicating Test Suites

Easy Suite Duplication

Easily duplicate test suites and change URLs across different environments.
1

Open the action menu

Click on the action menu of the test suite and select duplicate.
2

Specify duplication instructions

When duplicating the test, you’re able to:
  • Rename the suite
  • Remap URLs to different addresses
  • Leave forms blank to keep original URLs

​
Suite Types and Patterns

Quick Health Checks

These are your “is the building on fire?” tests:
  • Run quickly and check core functionality
  • Include login, basic navigation, and critical user flows
  • Designed to give confidence that the application is basically functional

​
Suite Execution and Orchestration

Keystone’s AI determines the optimal execution strategy:
  • Tests that don’t interfere run in parallel for speed
  • Tests with dependencies run sequentially for reliability
  • Automatic configuration based on test relationships
Different responses based on suite purpose:
  • Smoke tests might stop immediately on failure (fail-fast)
  • Regression tests continue to gather maximum information
  • AI learns from preferences and suggests appropriate handling
Suites coordinate resource usage to prevent conflicts:
  • Exclusive access to test databases
  • External service scheduling
  • Automatic conflict prevention

​
Best Practices

Logical Grouping

Group related tests together in a suite

Clear Dependencies

Establish clear relationships between tests

Maintainable Size

Keep suites focused and manageable

Regular Execution

Run suites frequently to catch issues early

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.

​
Advanced Suite Patterns

Nested Organization

Create suites of suites for complex scenarios:
  • “Full regression” suite includes feature-specific suites
  • Integration suites and performance suites as components
  • Nested organization for better structure