Unit Testing Deconstructed
summary
Argues a unit is a cohesive module and a unit test proves behavior while running isolated from other tests. Traces TDD back to Kent Beck and Test Driven Development by Example, noting Beck’s practical definition: tests that run in isolation. Evaluates four test qualities — behavioral, structure-insensitive, isolated, writable — and shows concrete trade-offs: heavy mocking yields isolation and behavioral checks but is structure-sensitive and hard to write; registering a mock database plus a builder reduces brittleness but can hurt readability and speed. Advises choosing trade-offs and matching tooling to goals.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:17What is a unit?
- 5:17Principles of cohesion
- 8:57TDD and behavior testing
- 13:50Desirable test qualities
- 17:27Managing test trade-offs
- 19:56Conclusion and resources
