Skip to content
Help Center
Browse documentation

Run only the tests for areas that changed

After a release, pick the pages and flows you changed and TestOptim runs only the test cases that cover them, saving time and executions.

Updated 3 min read
In this article

To run a regression check after a release in TestOptim, click Run changed only on the Test cases page, tick the pages and flows you changed, and run just the test cases that cover them. You do not need to run your whole suite after every small change.

Before you start

  • You need the QA Engineer role or higher.
  • The project needs generated test cases (see Generate test cases).
  • No other run or exploration can be in progress for the project.

Run the tests for what changed

  1. Open your project and select Test cases.

  2. Click Run changed only in the page header.

  3. In the What changed? dialog, tick the pages and flows you changed. Each line shows how many test cases cover it, and the list scrolls if you have many.

    What changed dialog listing pages and flows with test counts, one ticked, and a summary line reading Will run 4 of 95 tests
    The summary line shows how many tests will run and a rough duration.

  4. Check the summary under the list: Will run N of M tests with an estimated time.

  5. Click Run N tests.

TestOptim shows Test run started for N changed area(s) (N is the number of areas you ticked, not tests) and takes you to the Test runs page, where it appears as a Targeted run. Follow it as described in Run your tests.

Warning

If you tick nothing, the button changes to Run full suite and the summary shows the size and estimated time of the whole suite. The full suite is also trimmed to your remaining executions, unlike a targeted run. Check the button label before you click.

What gets included

  • Generated cases only. The list is built from the pages and flows your test cases were generated from. A case is included when it was generated from something you ticked.
  • Manual cases are never included. Cases you added manually are not tied to a page or flow. They show up in the list as (unattributed), but ticking only that entry finds nothing to run (see below).
  • Excluded cases are skipped, as in every run.
  • Quota is not trimmed when you tick areas. Each test uses one execution. If you have fewer executions left than the number of tests, the run does not start and you see a message that you have reached your limit, rather than a smaller run. See Run your tests.

If nothing matches

If the pages or flows you ticked do not match any included test case, TestOptim does not start a run and no executions are used. You see an error like this:

Error message: No test cases cover (unattributed). Re-run without changedAreas to run the full suite.
The wording mentions changedAreas, which is the name of this option in the API. In the app, untick everything to run the full suite, or pick different entries.

Pick other entries, select cases yourself and click Run (see Run your tests), or run the full suite.

Keep reading