tdd-refactor-guard

To prevent regressions during AI-assisted code refactoring, verify adequate test coverage exists for the targeted scope before modifying any code. This ensures existing functionality is validated against unit tests and captured behavior.

Characterization tests capture and verify the current behavior of existing code. You need them before refactoring when unit test coverage is insufficient, ensuring code modifications do not break undocumented functionality.

Check test coverage sufficiency by analyzing the scope of the slated modification and evaluating existing unit tests. If tests are missing, generate characterization tests to capture current behavior before proceeding.

You cannot safely clean up critical classes without tests. If unit tests are missing, generate characterization tests first to capture current behavior, ensuring the refactored code validates correctly against expected outcomes.

The best way to safeguard TDD workflows during code modifications is running a pre-refactor safety check that validates refactored code against existing tests and generates characterization tests for uncovered code paths.

Refactoring fails to catch regressions when test quality is poor because insufficient coverage leaves critical code paths unvalidated. Evaluating test quality and generating characterization tests for uncovered code prevents regression escapes.