Don't write a lot of tests!
summary
Argues that a smaller, tightly focused e2e suite beats thousands of brittle tests by delivering fast, narrow feedback in CI; gives concrete numbers from past jobs (3,600 nightly Selenium tests, ~1,000 mixed tests) to show maintenance pain, recommends using Cypress Cloud’s flaky test reporting to find culprits, pruning or isolating slow suites to meet a time threshold, tracking bug-vs-maintenance failure ratios, and the blunt rule: delete your bad tests and prefer short feedback cycles.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:01Modern testing paradigms
- 4:53Problems with too many tests
- 6:43Overnight regression tests
- 7:40Test fidelity and trust
- 10:06Failure fatigue
- 12:14Strategies for fewer tests
- 14:55Delete bad tests now
- 16:22Q&A session
related talks
55mUnit tests are useless. Change my mind
26mKeeping Your Tests Lean
34mStop hating your test suite!
17mWrite tests. Not too many. Mostly integration.
39mMastering UI tests
28mEgad! How Do We Start Writing Better Tests?
29mEgad! How Do We Start Writing (Better) Tests?
48mThere is Such a Thing as Too Much Testing