Pain Is Over, If You Want It
summary
Recounts how a grassroots push at Google makes automated testing a default: a GS policy of no changes without tests, continuous builds, coverage monitoring and mentor teams (test mercenaries) that scale tooling. The result: ~15,000 devs across 4,000 projects making 5,500 changes/day and ~75 million tests/day (~868 tests/sec). Shows healthcare.gov rescue leading to 8 million enrollments by April 2014 and describes 18F tooling like the Hub, team API and about.yaml to replicate that culture in government.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:30Healthcaregov
- 1:20How does it stay fixed
- 2:54The threat
- 3:38Google Web Server
- 6:30Value of a Negative
- 7:58Culture Change
- 10:41Automated Testing
- 12:29Testing Group
- 13:53Testing on the Toilet
- 16:43Fixit
- 17:49The Bridge
- 20:14What Did This Enable
- 22:10The Government
- 25:24Organizational Forces
- 26:18Inferiority Complex
- 27:33Lack of Communication
- 29:18The Hub
- 30:33Working Groups
- 33:18The Ask
related talks
38mGoogle's DevOps Culture
28mGrowing Pains - What happens when your product gets BIG?
30mDevOps and the Healthcare Giant
48mDevOps Culture & Practices to Create Flow
53mIf Government can do it...
53mTransforming testing methodologies: From manual to robust strategies
47mHow to win in software development with tighter feedback loops
42mOperability and You Build It You Run It