Test impact analysis
6 min readLast updated 2026-04-26New
Only run tests affected by your code changes. Cut CI time by up to 80% on large suites.
Test impact analysis maps tests to source files using static analysis and runtime traces. When a file changes, only the relevant tests run.
How it works
- 1Check Studio instruments your app during test runs to build a dependency graph
- 2On subsequent runs, it compares the changed files against the graph
- 3Only tests with affected dependencies are scheduled
Enabling
checkstudio run --impact-analysisLimitation
Impact analysis works best for monorepos and component-based architectures. It may over-select tests in highly coupled codebases.
Was this article helpful?
Still have questions?
Our support team is here to help. Reach out directly or search the docs.