Run Changed and Failed Tests

Run Changed and Failed Tests

Run Changed and Failed Tests

Sep 30, 2025

Sep 30, 2025

21.138.0

24.0.0

Re-run only changed and failed tests from a previous run to speed up feedback, reduce load, and use concurrency more intelligently.

Re-run only changed and failed tests from a previous run to speed up feedback, reduce load, and use concurrency more intelligently.

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:

  • Tests that failed

  • Tests that have changed since that run

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.

Faster feedback without wasted capacity

In most automation setups, rerunning a suite means rerunning everything.

That consumes:

  • Runner concurrency

  • Environment resources

  • Test data

  • Team time waiting for results

Run Changed and Failed Tests narrows the scope automatically so you can:

  • Keep runner concurrency free for other tasks

  • Reduce unnecessary test data creation

  • Lower load on your environments

  • Get faster, more focused feedback

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.

Built for real-world automation workflows

Large test suites demand intelligent execution.

Run Changed and Failed Tests helps teams:

  • Debug faster

  • Reduce operational drag

  • Protect environment stability

  • Improve overall efficiency

As an added benefit, rerunning only what is necessary is a greener option than executing a full suite again.

Less waste.
More focus.
Smarter test execution.