aibdd.auto.php.it.refactor

Safe PHP refactoring requires a coordinated two-phase workflow that keeps tests green throughout. You start by refactoring test code for readability, then refactor production code applying SOLID principles and strict typing, ensuring all tests pass at every step.

The two-phase PHP refactor workflow separates test code improvements from production code changes to maintain green tests. Use it for mid-size PHP projects needing progressive improvement of testability and maintainability while preserving existing behavior.

To apply SOLID principles and strict typing during a PHP refactor, execute Phase B after test refactoring. This phase enforces strict types, type hints, and safer patterns in production code while continuously verifying that all tests remain green.

No, you should refactor test code first in Phase A before touching production code in Phase B. Refactoring tests first improves readability and removes redundant patterns, establishing a reliable green test baseline to safely guide subsequent production code changes.

Code quality constraints enforced during a PHP refactor include strict typing, SOLID design principles, type hints, and safer structural patterns. These guidelines ensure improved testability and maintainability without altering the application's external behavior.