Google, quality and you
summary
Google runs a single monolithic repo with ~9 million source files and ~2 billion lines of code, 45,000 commits per day, and everything built from head, so tests must catch breakage early. Tests get sized: small tests <1s, medium between, large >2min (and “enormous” for hours). Flakiness sits at about 1.5% flaky overall; mitigation includes tagging flakes, automatic retry three times, recording flake probability and quarantining tests above thresholds, and pushing for hermetic, independent tests with no external side effects.
AI-written summary · about
chapters (5)
- 0:00Start
- 23:54Medium Test
- 25:38Test Pyramid
- 42:51External Dependencies
- 43:22What Is the Main Reason of Flakiness in a Google
related talks
46mThe state of the Art in Tackling Flaky Tests
28mThe State of Art in Tackling Flaky Tests
01h 04m“All Your Tests are Terrible..."
26mKeeping Your Tests Lean
41m0Flake - Reaching reliable non-flaky tests
44mThe Hell of Automated Tests
31mYour Tests Aren’t Flaky, You Are!
38mSquash the Flakes! – How to Minimize the Impact of Flaky Tests