Refactoring

Edit Answers
1234567891011121314151617
Across
  1. 5. A framework/library that helps with characterized tests.
  2. 7. Improve code structure without changing its behavior.
  3. 8. A strategy to understand why code fragments are affected by change.
  4. 12. A code smell where primitive types are overused instead of objects.
  5. 14. Strategy to understand the code by commenting and drawing relations
  6. 16. A pattern that ensures only one instance of a class exists.
  7. 17. A point that you need to modify to implement a feature or refactoring.
Down
  1. 1. A point in legacy code where you can experience the impact of your change.
  2. 2. A code smell where logic is repeated.
  3. 3. A code smell where a class depends too much on another class’s data.
  4. 4. Tests that document existing behavior before refactoring.
  5. 6. Old, difficult-to-maintain code that lacks proper tests.
  6. 9. An indicator of deeper design problems in code.
  7. 10. The level of dependency between different parts of a system.
  8. 11. The process of verifying software behavior.
  9. 13. A type of variable used to observe hidden behaviors in legacy code.
  10. 15. A refactoring technique that pulls out smaller methods.