Testability: when your testing problem isn’t testing
summary
Claim is that hard testing signals a design problem not a testing one and the fix is concrete changes not more tests If it is hard to test we have built it wrong. Teams put automated suites into a CI pipeline so fragility and slowness become visible, swap pixel‑based checks for SVG/DOM queries to eliminate brittle image asserts, and add targeted logging to improve observability controllability smallness. Result is fewer flaky tests less maintenance and faster feedback loops.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:29Automated testing paradox
- 5:26If it’s hard to test we build it wrong
- 6:30Testability, observability, controllability
- 9:20Q&A
- 12:07Developer collaboration for testability
- 13:50Prioritizing testability
