Related features
Run Changed and Failed Tests
Re-run only changed and failed tests from a previous run to speed up feedback, reduce load, and use concurrency more intelligently.
Run history
Track test health over time with full visibility into passes, failures, duration, and time saved across every run.
Trigger multiple packs
Run the same Flows with multiple value sets via Recipes or CI/CD to maximise coverage across environments, languages, and configurations.
21.27.0
Terminate Tests & Runs
Stop runs instantly when you need to
With Terminate Tests and Runs, you can immediately stop active tests or entire runs, even after they’ve started executing.
No more runners tied up on work that no longer matters.
Stop runs instantly when you need to
No more hogging runners that could be delivering you value elsewhere.
Free up runner concurrency for higher priority work
Free up runner concurrency for higher priority work
Keep runners focused on tests that move the needle
Avoid blocking other team members
Maintain fast feedback loops
Less load on staging or production-like environments
Fewer unwanted records created during test execution
Reduced database noise
Cleaner environments for subsequent runs
Reduces unnecessary resource consumption
Lowers infrastructure overhead
Keeps automation focused on what matters
Protect runner concurrency
In parallel testing environments, runner availability directly impacts release speed. Keeping capacity aligned with meaningful work is critical.
Less load on staging or production-like environments
Reduce environment load and test data pollution
Fewer unwanted records created during test execution
This keeps your systems stable and easier to maintain.
A cleaner and smarter way to test
Running tests you no longer need wastes compute, infrastructure, and time.
Smarter automation is not about running more tests.
It is about directing effort where it delivers real value.
