Thinking in tests
summary
Argues that test-driven development is a rapid cycle of testable hypotheses exercised with xUnit/JUnit and continuous integration, driving small red–green–refactor steps that enable safe, frequent refactoring and evolutionary design. Gives concrete results: a C embedded team produces 51 defects vs ~460 expected, teams ship without manual QA, and a demo builds a retirement projection in 25 hours while a startup ships a Google Docs precursor in two weeks — tests enable change and keep things working.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:37What Test-Driven Development
- 9:20Refactoring
- 11:53Testable Hypothesis
- 14:04Test-Driven Development and Extreme Programming
- 18:23Domain-Driven Design
- 20:06Evolutionary Design
