Pragmatic Testing
summary
Defines “change tests” and presents concrete patterns to avoid them by refactoring fragile assertions into stable contracts. Shows how separating unit and integration concerns and extracting test fixtures into reusable helpers reduces churn, preserves regression value, and gives repeatable practices for asserting behavior rather than implementation; includes guidance on when to update tests and how those choices lead to simpler, safer API designs.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:59Practical testing
- 25:16Effective test design
- 35:00Test schemas
- 43:34Severity vs coverage
- 48:58Q&A
