Skip to content

Test impact analysis#

Test impact analysis finds automatically a minimum set of tests that can verify changed code.

The Rise of Test Impact Analysis

On module level#

Besides tests, we have different work to do in modules: Android Lint, unit-tests, assemble, ...
If a module is not affected by changes, we don't want to run anything in it.

graph TD AppX --> FeatureA AppX --> FeatureB AppX --> FeatureC AppY --> FeatureC AppY:::changed --> FeatureD:::changed classDef changed fill:#f96;

These optimizations are supported in CI Steps Plugin.
See implementation in impact module.