From Implementation TDD to Behavior TDD
summary
Argues that Implementation TDD produces many brittle, slow unit tests — e.g., five internal entities each needing their own test suites, one implementation chunk taking an hour and multiplying effort — and those tests break on refactor. Proposes Behavior TDD: write a single acceptance flow for the user buying an item that asserts item removal, payment recorded, invoice persisted, notification delivered and user authenticated. Uses the red‑green‑refactor cycle and reports faster delivery and fewer broken tests after refactors.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03What is Implementation TDD
- 3:12Problems with Implementation TDD
- 6:33What is Behavior TDD
- 9:35Red-Green-Refactor Workflow
- 12:03Feature Lifecycle
- 13:56Key Takeaways
- 14:37Q&A
