Suites and Play All
Group approved tests into suites such as Smoke or Checkout, choose the site, order and parallelism, and run the whole suite with Play All before every release.
A suite is a named set of approved tests that you run together. Most teams start with a quick Smoke suite and add one per area, such as Checkout, Account and Admin.
Create a suite
- Open Suites (Play All) in the sidebar and press New suite.
- Give it a name and, optionally, a description, for example "Run before every release".
- On the suite page, add tests from the list on the right. Only approved tests can run; drafts in a suite show Not approved — will be skipped.
Suite settings
| Setting | What it does |
|---|---|
| Default environment | The site the suite runs on unless you choose another when you press Play All. |
| Max parallel | How many tests run at the same time (up to your plan's limit). Higher is faster; lower is gentler on a small staging server. |
| Run in this order | Runs tests one after another in the listed order, for flows that build on each other. |
| Stop on first failure | Skips the remaining tests as soon as one fails, which is useful for a quick smoke check. |
Press Save settings after changing them.
Prefer independent tests that can run in any order. They're faster in parallel, and one failure doesn't cause a cascade. Use Run in this order only when a flow really depends on a previous one.
Run it
Press Play All. A progress page shows each test's status as it runs, with totals for passed, failed, running and skipped. You can leave the page and come back; the batch keeps running.
- Retry N failed re-runs only the tests that failed, which helps separate real failures from one-off glitches.
- Cancel all stops every queued and running test in the batch.
Recent Play All runs are listed on the suite page, so you can see whether a suite was green before a release.
Running everything
You don't need a suite to run many tests: on Tests, tick the box at the top of the list to select every approved test, then press Run selected.
Tests over your plan's limit
If your workspace has more saved tests than its plan allows (for example after a downgrade), Play All runs the tests within the limit and marks the rest Skipped with the reason. See Plans, usage and limits.