Program with GUTs
summary
Asserts that the common pattern of one test per method is wrong and increases test maintenance debt, demonstrates concrete examples using a stack to show one method one test is wrong, shows how JUnit 5 display name generation and nested tests and equivalents in pytest and Jest let tests read like specs, extracts a small state model (new, empty, nonempty) and builds grouped tests that reflect properties and transitions, and claims the result is clearer, fewer fragile tests and a sustainable test suite.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker
- 1:54Importance of quality tests
- 3:59Problem with method-aligned tests
- 8:14Behavior-driven test naming
- 11:02Language-specific adaptations
- 12:29Grouping by state transitions
- 13:53Conclusion and resources
