How to Stop Hating Your Test Suite
summary
Argues that consistency fixes most test pain and offers a ready-to-fork Test Style Guide with concrete rules: limit objects to one public method and at most three dependencies, split suites into an isolated unit suite and an integrated end-to-end suite, and prefer given when then style for clearer failures. Demonstrates a 4‑boolean example → 2^4 = 16 permutations, describes a directory-migration trick to start fresh, and notes a JS test double library and feedback budgets (480 minutes per day baseline).
AI-written summary · about
chapters (8)
- 0:00Start
- 12:09take advantage of the expressiveness of our spec
- 12:36try to minimize each phase to just one line per action
- 22:54create separate test suites
- 30:01detect redundant coverage
- 30:36identify a clear set of layers to test
- 32:49use the test as a sounding board
- 42:33use fixtures for integration tests
