How deep are your tests
summary
Argues that you must minimize end-to-end tests and prefer unit tests with mocks and stubs to avoid combinatorial blowup — e.g. three branches of 3×8×5 produce 120 paths but stubbing collapses that to testing individual parts (sum of branches). Shows a concrete VAT rule example: mock the rule engine, stub org number 5569215576 to return Feb 28, then implement provider to match the stub. Notes Selenium-driven UI tests are slow and brittle.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:44Who Are We Testing for
- 4:16Integrated Tests
- 7:32Diagnosis Speed and Confidence
- 14:28Death of Field
- 15:54The Testing Cone
- 20:57Unit Tests
- 24:32Verify Interaction
- 36:14Outside in Development
- 39:26Recap
- 39:44Conclusion
