Pragmatic Not Dogmatic
summary
Argument: tests only help when they target the right scenarios and evolve with the code. Evidence: an 85% coverage rule produces empty or fake asserts (85% coverage trap), unit tests alone find ~30% of bugs, but combining techniques can exceed 90%. Practical rules: refactor tests as well as production code, throw away legacy tests that block change, alternate fast test/code cycles with occasional spikes for architecture. Observed behaviors: frequent small floss versus root canal refactorings and guarded use of GUI tests.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:19Test-driven development
- 9:15TDD promises challenged
- 14:09What tests really do
- 23:54TDD beyond unit tests
- 31:56Fast and slow thinking
- 41:26Tests first always?
- 49:29Safe code changes
- 56:30Tests and quality code
- 1:06:45Unit tests not enough
- 1:12:01Dogmatic vs pragmatic
- 1:16:44Q&A
