Related features
Run recipes
Create reusable run configurations to test different environments, tags, and value sets. Trigger complex test selections without editing code or pipelines.
Trigger multiple packs
Run the same Flows with multiple value sets via Recipes or CI/CD to maximise coverage across environments, languages, and configurations.
Terminate Tests & Runs
Stop tests and runs after they've started. Free up runners, reduce environment load, and avoid wasting time or concurrency.
21.138.0
Run Changed and Failed Tests
Re-run only what matters
When a run fails, you rarely need to execute everything again.
With Run Changed and Failed Tests, DoesQA lets you start a new run based on an existing run, including only:
Re-run only what matters
All values and environment information from the original run are preserved. You are not starting from scratch. You are continuing with full context.
To use it, drill into a completed run and select Run Changed and Failed Tests. The new run is created with the same configuration and input data.
Tests that failed
Tests that have changed since that run
Runner concurrency
Environment resources
Test data
Team time waiting for results
Keep runner concurrency free for other tasks
Reduce unnecessary test data creation
Lower load on your environments
Get faster, more focused feedback
Debug faster
Reduce operational drag
Faster feedback without wasted capacity
In most automation setups, rerunning a suite means rerunning everything.
Run Changed and Failed Tests narrows the scope automatically so you can:
Built for real-world automation workflows
If failures continue, you can repeat the process on the resulting child run. Each iteration becomes more targeted, allowing you to focus on just the tests that still need attention.
As an added benefit, rerunning only what is necessary is a greener option than executing a full suite again.
