Structure and Interpretation of Test Cases
summary
Argues that good unit tests act as readable specifications, not mere framework exercises, using JUnit 5, Catch and parameterized/data-driven tests to show what to name, nest and group. Demonstrates with a leap‑year implementation (naive modulo‑4 fails — tests reveal the 4/100/400 classification and the surprising fact that only ~5–10% of developers know the full rule; ~75% of years are non‑leap), plus stack and queue ADT specs. Emphasizes propositional test names, given–when–then narratives and nesting/grouping over mock-heavy or over‑refactored tests.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:21Title
- 1:03Target Audience
- 2:03XUnit Test Patterns
- 3:00Test Code vs Production Code
- 4:31Documentation
- 5:00Language
- 6:12Guts
- 6:36Unit Tests
- 13:43Leap Year
- 17:36Constructive Advice
- 18:41Examples
- 19:32Improvements
- 20:28Naming Conventions
- 26:45Propositions
- 29:09Commonality
- 29:27Nesting
- 30:34Test Data
- 32:30Multiples
- 33:43Over Programming
- 38:03Stacks
- 38:33Abstract Data Types
- 44:56Strunk and White
- 45:13The assert statement
- 46:04The name
- 46:28Naming
- 47:24Stack Specification
- 48:09Preconditions
- 48:46Deep Observation
