Change untested code without gambling on regressions.
legacy code maintenance
Guides safe, incremental changes to untested code by establishing tests and breaking dependencies before modifying behavior.
When to use it
Use when changing or testing legacy or untested code, especially when dependencies obstruct a test harness.
Give it a change in an untested project; it identifies test points, establishes coverage, and makes the change incrementally.
What you provide
No additional actions listed in the analysis.
No setup requirements listed in the analysis.