Get Out of the Legacy Rut with (Test-)Capture(s)
summary
Explains how to introduce test-driven development and testing practices into legacy codebases with dependencies, code smells, mixed architectures and tight deadlines by using “capture tests” (and other techniques). Describes concrete approaches to write tests that safely record and stabilize existing behavior so teams can refactor and add tests without long freezes or frightening colleagues.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 13:23Kata presentation
- 45:34Legacy code exploration
- 1:08:44Golden master concepts
- 1:25:50Characterization tests
- 1:56:54Conclusion
related talks
21mShaky to solid a test based approach to legacy code
36mUsing Tests as a Tool to Wrangle Legacy Projects
47mTest Driven Traps
45mTesting Legacy Code - What To Do When It Seems Untestable
40mTesting Legacy Code: Safe Refactoring
01h 01mYou Can Test Anything
36mReversed Test Pyramid — Dealing with Legacy Code
34mTesting legacy code when you dislike tests (and legacy code)
