tdd-refactor-guard

To verify test coverage before an AI-assisted code refactor, evaluate the public API surface, dependencies, and side effects. This process checks existing tests to ensure adequate coverage and prevents regressions during automated modifications.

Characterization tests capture and lock in the current behavior of existing code. You need them for refactoring when current test coverage is insufficient, allowing you to safely modify code without altering its original outputs.

Safeguard your codebase against refactoring regressions by enforcing a pre-refactor safety check. This validates that existing tests cover the targeted code, assessing API boundaries and side effects before any AI modifications are applied.

Yes, you can generate missing tests automatically before modifying code. When pre-refactor analysis reveals insufficient test coverage, characterization tests are generated to preserve current behavior before proceeding with changes.

You need existing tests to initiate a safe AI-assisted refactor. If the evaluation finds the current test coverage insufficient for the targeted code, the guard can generate characterization tests before proceeding.

The best way to scope refactors safely is to assess the public API surface, dependencies, and side effects of the targeted code. This ensures modifications are contained and covered by adequate test verification.