Batched Execution¶

Overview¶

Tests within a suite can be executed in batches, enabling parallel processing across multiple workers. This significantly reduces the total time needed to run large suites.

How it works¶

Tests are split into batches of 5 (current default)
Each batch runs as an independent parallel task
All batches execute simultaneously across multiple workers

Example: a suite with 20 tests runs as 4 parallel batches, with 5 tests in each batch.

Exploration batches¶

For exploration tests, batches can cover different themes or focus areas. This lets you explore multiple parts of your application at the same time, increasing coverage per run.

For large explorations, the product may offer parallel batches (up to 5 flows per batch, similar in spirit to suite batching) versus a single batch — you can choose what fits your run.

Credits¶

Credits are reserved upfront for the full run when batched execution starts. If you stop the execution early, any unused credits are immediately refunded.

Triggering batched execution¶

You can enable batched execution via the External API by setting allow_parallel to true in the run-tests request.