Composite Test Suites
Combine multiple test suites into a single executable flow for comprehensive end-to-end testing.
Composite Test Suites
Composite test suites allow you to combine multiple existing test suites into a single, unified test run. This is useful for creating comprehensive test scenarios or grouping related tests together.
What Are Composite Suites?
A composite suite is a collection of other test suites that run together as a single unit. When you run a composite suite, all included suites execute in sequence.
Use Cases
Smoke Test Suite
Combine critical tests from across your application into a quick smoke test that verifies core functionality.
Regression Suite
Bundle all test suites for a complete regression test before deployments.
Feature Grouping
Group tests by feature area (authentication, checkout, admin) for targeted testing.
Browser-Specific Testing
Create composites for cross-browser testing with suites that have browser-specific configurations.
Creating a Composite Suite
Go to Test Suites in the sidebar.
Click the Merge Suites button in the create options.
Give your composite suite a descriptive name (e.g., "Full Regression Suite").
Choose which existing test suites to include in the composite.
Arrange the execution order if sequence matters.
Save your composite test suite.
Identifying Composite Suites
Composite suites are marked with a special badge in the Test Suites list:
- Look for the Composite badge on suite cards
- The suite card shows the count of included suites
Running Composite Suites
Running a composite suite works just like running any other suite:
- Click Run on the composite suite
- Select a browser (Chromium, Firefox, or WebKit)
- All included suites execute in sequence
- View combined results in a single test run
Composite Suite Results
When viewing results of a composite run:
- Overall pass/fail status based on all tests
- Breakdown by included suite
- Individual test results within each suite
- Total duration (sum of all suite durations)
Managing Composites
Edit a Composite
Click Edit on a composite suite to:
- Add or remove included suites
- Change the execution order
- Rename the composite
Nested Composites
You can include a composite suite inside another composite, creating nested test hierarchies.
Best Practices
- Create a "Smoke Test" composite with your most critical tests
- Build composites for each deployment stage (dev, staging, production)
- Keep composites focused - don't include every test
- Consider execution time when building large composites
- Use composites for scheduled nightly regression runs
- Name composites clearly to indicate their purpose
Example Composite Structure
Full Regression Suite (Composite)
āāā Authentication Suite
ā āāā Login tests
ā āāā Logout tests
ā āāā Password reset tests
āāā Product Catalog Suite
ā āāā Product listing tests
ā āāā Search tests
ā āāā Filter tests
āāā Checkout Suite
ā āāā Cart tests
ā āāā Shipping tests
ā āāā Payment tests
āāā Account Suite
āāā Profile update tests
āāā Settings testsComposite vs User Flow
| Feature | Composite Suite | User Flow |
|---|---|---|
| Purpose | Bundle existing suites | Multi-page journey |
| Failure behavior | Continues to next suite | Stops on failure |
| State sharing | Independent contexts | Shared browser context |
| Best for | Regression testing | End-to-end journeys |
Related Documentation
- Running Tests - Execute test suites
- User Flow Tests - Multi-page journeys
- Scheduling Tests - Automate composite runs