Authoring Guide

Suite management

Suites are folders for organizing tests. Multi-suite membership and three filter modes (All / By Suite / Unassigned).

A suite is a folder for grouping tests. Suites are organizational only — running a suite runs each of its tests sequentially, but a test doesn't change behavior based on which suite it's in. A test can belong to multiple suites or none.

Creating a suite

Create a suite from the test list view. Each suite has a name and a color.

Assigning tests

A test can belong to multiple suites or to none.

A test in zero suites is Unassigned.
A test in one suite shows that suite's color tag.
A test in multiple suites shows multiple tags.

Filtering the test list

The test list filter has three options:

All — show every test.
By Suite — show tests in the selected suite.
Unassigned — show only tests not in any suite.

Use Unassigned to find stray tests that escaped your organization scheme.

Test list view with the suite filter chip showing 'Suite: Login flows' selected, the suite list popover open with five suites visible (each with their preset color circle), and one test card showing two color tags.

Running multiple tests in a suite

Suites are organizational only — there's no "play whole suite" button. To run a sequence of tests as one unit, build a parent test that calls each member with Run Test steps. See Reusing logic — Run Test vs. User-Defined for the composition pattern.

Common patterns

Per-feature suites. "Login flows", "Onboarding", "Checkout", "Settings" — match your app's feature areas.
Per-stability tier. "Smoke", "Regression", "Flaky" — segregate tests by how seriously a failure should be taken.
Multi-membership for cross-cutting needs. A "Smoke" suite can include tests that also live in their feature suite, so the smoke run is curated without duplicating tests.