working-with-legacy-code

To refactor legacy code without tests, apply a cover-and-modify discipline using characterization tests to pin down existing behavior, then isolate dependencies using techniques like Extract Interface to ensure structural changes do not cause regressions.

A characterization test is a snapshot or golden master test that captures and verifies the current behavior of untested codebases. You need it before modifying or refactoring complex monolithic systems to ensure existing outputs remain unchanged.

You isolate dependencies in a monolithic system by applying mechanical dependency breaking techniques, such as Extract Interface and Parameterize Constructor, to identify seams and decouple code for targeted testing.

The best way to add features to legacy code without a full rewrite is through incremental test coverage. Use dependency breaking to isolate modules, pin current behavior with characterization tests, and safely add features through the cover-and-modify algorithm.

Yes, you can safely modify untested code by writing targeted characterization tests only for the specific module you are changing. This incremental approach isolates dependencies and pins behavior without requiring complete test coverage upfront.

Modifying untested legacy code causes regressions in monolithic systems because tightly coupled dependencies hide behavioral interactions. Without characterization tests to pin down existing behavior, structural changes inadvertently alter downstream outputs.