Continuous Testing at Scale
summary
Continuous testing at scale requires concrete fixes: an open-source toolset called TAS from LambdaTest that runs test impact analysis to map commits to affected tests, proactive flaky-test detection using mutation testing, randomized ordering and automated reruns (Netflix reruns up to 35 times), plus dashboards that surface skipped vs long-failing tests. The claim is measurable: reduce needless full-suite runs, surface 1.5%+ flaky patterns, and cut execution time by only running impacted tests.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:47Where does continuous testing fit in?
- 2:31Too many Tests little time
- 2:49Flaky Tests
- 3:37What do you do?
- 5:14Proactive testing for flakiness
- 8:26Test Impact analysis
related talks
24mOrchestrating automation tests for Continuous testing
56mTesting at scale
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
25mHow to ensure Testing Robustness in Continuous Testing Environments
32mTest Automation and Beyond: Implementing Continuous Testing Effectively
30mBest Practices for Accelerating Continuous Testing
44mStrategy for Acing Continuous Testing in DevOps
34mWhy continuous testing is essential