My 19 Laws of Test Driven Development
summary
Claims a concrete TDD recipe for .NET: align test scope with functional slices instead of testing every class, include real database when a type’s job is DB interaction using SQL LocalDB or containers, and test HTTP APIs by sending HTTP requests and asserting responses not by instantiating controllers. Recommends test data builders, AAA or Given/When/Then styles, fewer internal interfaces, characterization tests for legacy code, watches coverage (80–90% reasonable) and cites a library with ~97% coverage as proof these heuristics work.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 2:06TDD productivity plateau
- 3:29Designing for testability
- 5:13Code by functional slices
- 6:59Dependency inversion
- 7:41DRY within boundaries
- 8:45Test scope alignment
- 10:08Reusable components testing
- 11:11HTTP API testing
- 13:58Databases in unit tests
- 15:45Test structuring styles
- 16:48Unit vs integration tests
- 17:32Test code quality
- 18:36Tests as documentation
- 19:38Avoiding interfaces
- 20:41Dangers of over-mocking
- 22:04Clear test failures
- 23:30Test data builders
- 24:33Tests fail first
- 25:39Test readability
- 26:43DTOs in assertions
- 27:45Debugging tests
- 28:28Test naming and organization
- 31:18Q&A
- 34:28Q&A
- 35:54Q&A
- 37:41Q&A
- 38:44Q&A
