Testing Should Be Fun
summary
Argues that testing becomes enjoyable again by fixing concrete problems: slow CI (Groupon cuts suite from ~40 to 20 minutes), flaky tests, and bloated fixtures. Recommends specific refactorings: remove unnecessary DB hits (use new or factories for only changed attributes), split multi-step specs into smaller tests, extract shared setup, prefer single-assertion tests when sensible, assert on primitive values for clearer failures, use spies (Jasmine style) and run only changed files or focused suites to keep feedback fast.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:06Kent Beck and JUnit origins
- 4:36Programmers love tests
- 8:26Why testing gets painful
- 12:15TDD and long-term tests
- 16:33Test refactoring principles
- 21:25Extracting tests for clarity
- 24:59Removing DB hits
- 27:32Factories and test noise
- 31:06Cucumber and unit tests
- 32:54Single assertion style
- 34:18Right testing level
- 36:27Primitive assertions
- 37:53Jasmine spies vs mocks
- 39:18Meaningful test values
- 41:29Boolean test habits
- 41:49Easy test runs
- 43:59Listen to your tests
- 45:01Delete unnecessary tests
- 46:26Avoiding Uncanny Valley
- 47:08Resources and closing
