refactor

To refactor code safely, you use existing test coverage as a safety net to verify behavior preservation. The process requires passing lint and type checks, running tests after each minimal change, and updating tests for any intentional behavioral modifications.

You need existing tests, passing lint checks, and passing type checks to refactor a module while preserving functionality. Appropriate test updates are also required if the refactoring introduces any intentional behavioral changes during the process.

Test coverage acts as a safety net during code refactoring by validating that behavior remains unchanged after each step. Running tests alongside lint and type checks after every minimal commit catches regressions immediately.

Refactoring a function with incomplete test coverage is not recommended because tests are required as a safety net to ensure behavior preservation. You must have existing tests that pass lint and type checks before starting.

The best way to plan refactoring steps for a complex component is to make minimal changes per commit while ensuring behavior is preserved. Verify each step by running tests, linting, and type checks continuously throughout the process.

You should update tests during a code refactoring process when there are intentional behavioral changes. If behavior is preserved, existing tests should pass without modification after running lint and type checks.