Devs should love your tests
summary
Claims that got results: a cross‑team coverage heatmap for the “leaving a review” flow reveals an untested star‑only path and leads to replacing many UI checks with API tests and component tests so coverage reaches 100% for critical flows. Engineering has 5,000 Selenium tests with ~500 ignored flakes, developers rate confidence 1–3, deployments go from weekly to 15–20 times a day at one company. Practices: make tests atomic, readable, stack‑aligned, run ≈60 seconds, no retries, and surface actionable failures.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:30Team Structure
- 13:48Test Automation is a programming project. Treat it like one!
- 14:17Testing is the glue
- 17:24Test Automation Infrastructure should make it easy for anyone to create, maintain, run, and consume your tests and test results.
- 19:38Tests should be trustworthy
- 21:36Tests should be atomic and pragmatic
- 23:18Each test should run within 60 seconds
- 24:13Tests should stay in the stack
- 26:59Test failures should be actionable
- 31:12Don't let testing or processes get in the way of Quality.
related talks
56mThe End Game
26mThe Impact of Testing on a DevOps Pipeline
31mMeasure it or it didnt happen
42mDeveloper Joy: How great teams get s%*t done
46mThe state of the Art in Tackling Flaky Tests
37mUnderstanding the successes and the pain points of different testing strategies
27mQuest for Adequate Autotest Coverage
38mThere Are No Tests