Skip to main content
Run Mode controls whether tests in a group execute at the same time or one after another. By default, groups run concurrently.

​
Concurrent (default)

Tests are eligible to run together, subject to your workspace’s concurrent-run limit. Extra tests stay queued until capacity becomes available; Free workspaces execute one run at a time. Each test runs independently with no ordering guarantee. Best for groups where tests do not share state or depend on each other. If the group has a preparation test, it must pass before the other tests start, in either run mode.

​
Limit how many run at once

A concurrent group can cap how many of its tests execute at the same time, for example 2 against a staging environment that cannot take a burst of sessions. At most that many tests run at a time, and later tests still run when an earlier one fails. There is no ordering guarantee, same as any concurrent group. This is the difference from Sequential, which stops at the first failure. The cap is bounded by your workspace’s concurrent-run limit: the slider runs from 1 to that limit, and the top of the range means “follow the plan limit”, which is the default. If your plan later drops below a saved cap, the plan limit applies until you save a new value. The cap applies per group run. Two runs of the same group started at the same time (for example a schedule firing while a manual run is still going) each get their own cap, so together they can run twice the cap. Single-test runs are never affected.

​
Sequential

Tests run one at a time, in the order shown in the group. The next test becomes eligible only after the previous one finishes and still waits for workspace capacity. A failed test or an execution crash cancels the remaining tests. A blocked or individually cancelled test allows the sequence to continue. Use this mode when tests share application data or target an environment that cannot handle parallel sessions. Each test still gets its own browser or device session; use a preparation test for supported session reuse.

​
Set up Run Mode

  1. Open Project → Tests tab.
  2. Pick the group in the Test library rail on the left.
  3. In the Run tests row under the group name, open the first menu (it reads Sequentially or Concurrently) and pick the mode you want.
  4. With Concurrently selected, drag the Tests at once slider below the modes. It saves when you release it.
Mode choices save as soon as you pick them. Concurrent with the slider at your plan limit (for example 5 / 5) is the default. The API, CLI, and MCP expose the same setting as maxConcurrentRuns (null follows the plan limit).

​
Reorder tests

When a group is set to Sequential, a drag handle appears next to each test. Drag tests to reorder them. Changes save instantly.