Testing Your Testing Strategy
summary
A team at Netflix builds a new dashboard explorer inside an existing app and finds full end‑to‑end suites slow and brittle, slowing early iteration; they instead rely on static analysis, linting and type checking, smaller modules, code reviews, fast deploys and canary rollouts, and observability with Sentry, Datadog, Grafana. Unit tests target complex data logic; heavy end‑to‑end tests using Cypress, Puppeteer, Playwright are added only for core user flows before a general availability launch.
AI-written summary · about
chapters (7)
- 0:00Introduction and story
- 8:05Why testing feels inefficient
- 16:53Defining testing goals
- 20:50Unit vs end-to-end tests
- 26:50Balancing speed and confidence
- 30:22Revisiting your strategy
- 31:07Summary and closing
related talks
58mTesting Strategy - New Model, Better Outcomes
20mPanel Discussion on Testing
41mEnd-2-end testing without the pain
27mTest Effective Development - End 2 (What) End?
49mThe Whole Team Approach to Testing in Continuous Delivery
37mUnderstanding the successes and the pain points of different testing strategies
53mModern Web Testing: Going Beyond Selenium
26mModern Testing Practices in Frontend Applications