A Reflection on Software Testing
summary
Argues that testing succeeds when tests target isolated behaviors not implementation, uses simple immutable doubles like pretend rather than magic mocks, and organizes code with the onion architecture so application logic is testable without a database. Recommends concrete tools: pytest parametrize, pytest-watch and parallel runs for speed, and higher‑level e2e tools (Cypress or Selenium Base) for smoke tests. Gives real numbers: a team project at ~60% coverage and a side project at 100% to show practical confidence.
AI-written summary · about
chapters (4)
- 0:00Start
- 28:27limit the use of these complicated doubles in your test suite
- 29:54add a method to the stub
- 42:45run pi test over multiple cpu cores
related talks
42mUse testing to Develop Better Software Faster
28mEgad! How Do We Start Writing Better Tests?
20mThe Art of Testing
57mAdvanced Testing Techniques: Tips from the trenches
58mTesting Strategy - New Model, Better Outcomes
01h 05mMicrotesting
02h 46mThe Joy of Testing
20mEffective Testing Approaches for your Application with Cecelia Martinez