Keeping Your Tests Lean
summary
An old UI suite of 1,000+ tests becomes manageable by deleting redundant cases, splitting tests into feature sub-suites, and running classes in parallel so runtime is reduced from 12h to 1h. Flakiness is tracked in a Google Sheet, flaky tests are quarantine[d] or auto-rerun until fixed, and tests use dedicated environments and data-qa selectors to avoid CSS brittleness. Preference for lower-level integration tests and headless browsers keeps the suite fast and reliable.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:54Fast Test
- 3:06Legacy Tests
- 3:55The Challenge
- 4:50Build Monitors
- 5:49Why a Lean Test Suite
- 6:43How to Maintain Valuable Tests
- 8:25Evaluate Existing Tests
- 10:20Collaborate
- 11:35Test Code
- 12:13Reliable Test
- 13:43Monitoring Flakiness
- 14:30Separating Tests
- 16:14Test Selectors
- 16:54Independent Tests
- 17:48Fast Tests
- 18:43Deployment Pipeline
- 19:34Paralyse Test
- 20:27Avoid UI Tests
- 21:50Headless Tests
- 22:39Summary
- 23:23Tradeoffs
- 23:59Start Over
