Skip to content
BENIBIX Learn

Change Impact Analysis

Development🕸️ Code IntelligenceCode Analysis

Also known as Impact Analysis, Blast Radius, Code Change Impact

Working out what else a code change will hit, before you make it.

Think of it like

It is like asking which dominoes will fall. You ask before you push the first one.

Example

Lucy plans to change parseDate. Impact analysis lists 3 functions, 2 services and 9 tests that rely on it.

Why it matters

Most breakages come from a part nobody knew was linked. This finds the links first.

Definition

Change impact analysis works out what else a change will affect before you make it. It starts from the part you plan to change. Then it follows the call graph and dependency graph back to everything that uses that part. The result is a list of code, tests and services at risk. Teams use it to pick which tests to run and who to ask for a review.
Change one function, and its callers light up as affected.

Common mistake

Stopping at the code. A change can also break a saved file format, an API that others call, or a report.

Key takeaways

  1. 1
    Start at the change. The part you plan to edit.
  2. 2
    Follow back. Find everything that uses it.
  3. 3
    Act on it. Run those tests, ask those owners.