safe-code-change

To update tests after modifying production code, use a workflow that identifies affected tests via git diff and applies minimal test updates to align with new behavior. This ensures test synchronization without editing production code, keeping your validation pipeline intact.

The best way to find affected tests is using git diff to locate changed production files and searching test files for relevant imports. Once located, apply minimal updates to reflect the new behavior without reformatting or lint-fixing during the update step.

Test synchronization involves analyzing the git diff of production files, searching for tests with relevant imports, and applying minimal updates to match the new behavior. If changes are ambiguous, the workflow prompts for clarification before applying updates.

Yes, after updating tests to align with the new behavior, you can run the full validation pipeline to verify tests pass and catch regressions. This ensures your code changes don't break tests and maintains production stability.

No, test synchronization after a code change applies minimal updates only to test files without modifying production code. The workflow reserves reformatting and lint-fixing for the validation step, ensuring clean separation between test updates and production behavior.

You should prompt for clarification when code changes are ambiguous and the required test updates cannot be determined automatically. This prevents incorrect test modifications and ensures the updated tests accurately reflect the intended new production behavior.