Pragmatic Testing
summary
Shows concrete tactics: prefer checking outputs over internals, replace disk RAM with an in‑memory fake, and exercise the real CPU so tests stop mirroring implementation. Uses mockito, rx java and room test helpers; builds an rx errors rule to surface uncaught errors (finds ~2000 bad tests) and an annotation processor to generate test injection helpers. Reports tests shrink and speed up (mono repo ~1hr → ~20min). Advice: use value as boundary, write fakes, test the public API.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:04Zac Sweers Pragmatic Testing
- 1:33Pragmatic? Testing
- 3:16Non-Goals
- 28:43What about my architecture?
- 33:10What about state?
- 33:47Value is the boundary
- 35:04Fakes are worth writing
- 35:29Ship your fakes
- 36:19Tests should test the public API
- 36:56Semver your tests
- 37:42Test are prod code
- 39:11Failures should be designed for
