refactor

To refactor code without altering behavior, you identify opportunities like extract-method or rename, apply small deterministic changes, and verify tests stay green. This preserves outward behavior while improving maintainability.

The red-green-refactor workflow is a test-driven cycle where you write failing tests, make them pass, then polish the implementation. The refactor step focuses on extract-constant and simplification techniques to improve readability while keeping tests green.

Yes, a green test baseline is required before refactoring. You must run the test suite to confirm all tests pass, then apply small, verifiable changes step by step to ensure behavior remains unchanged throughout the process.

You apply extract-method and rename techniques by making small, deterministic changes to the codebase. Each refactoring step must preserve observable behavior, keep tests green, and be documented for auditing and review purposes.

The best way to document refactoring changes is to record each small step taken during the process. Versioning and documenting changes like extract-constant or simplification actions ensures the refactoring can be audited and reviewed effectively.

You should avoid refactoring code without a green test baseline. The process requires verifiable, small step changes to preserve outward behavior, which is impossible to confirm safely if the test suite is not passing beforehand.