TDD Revisited
summary
Argues TDD is about driving behaviors not isolating “unit tests,” and recommends writing developer tests that target the smallest observable behavior, use red‑green‑refactor, and avoid testing private methods. Recommends mocks only for IO/shared fixtures or speed, uses JUnit/xUnit/NUnit and warns SpecFlow/Cucumber/Fitnesse are costly unless customers write specs. Claims test‑first gives scope control, test‑after is for regression, estimates unseen rework ~30%, and aims for fast feedback under 30 seconds.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:13TDD fallacies and principles
- 11:51Developer tests vs unit tests
- 22:26TDD as discovery
- 33:18Behavior-driven development origins
- 39:17Customer acceptance tests pitfalls
- 44:35Testing after dev vs TDD
- 50:17When not to use TDD
- 57:02Summary
