1 / 5
A refactoring, by definition, changes structure while keeping external ___ the same.
-
-
-
-
Refactoring is behaviour-preserving: it improves internal structure without altering what the code does from the outside.
2 / 5
Breaking a large refactor into many small, safe steps lets you ___ frequently.
-
-
-
-
Small steps let you run tests and commit often, so any breakage is caught immediately and easy to undo.
3 / 5
Introducing an abstraction so old and new implementations coexist during a migration is ___.
-
-
-
-
Branch by abstraction lets you swap implementations gradually behind an interface, avoiding a risky all-at-once switch.
4 / 5
Keeping the test suite passing at every step is described as keeping the build ___.
-
-
-
-
A green build at each step proves behaviour is preserved, which is the safety net that makes aggressive refactoring possible.
5 / 5
Refactoring just the code you touch while delivering features follows the ___ rule.
-
-
-
-
The boy scout rule — leave the code cleaner than you found it — spreads refactoring incrementally without a dedicated rewrite project.