Large Scale Web-Testing on Virtual Machines
summary
Google runs about 1 million web tests a day by booting browser-equipped VM images on demand, using QEMU with kernel acceleration and keeping commonly used VM images cached and suspended so tests start in seconds. The system bundles a monitored Selenium server into each image, updates images quarterly but pulls newer jars at startup, scales from hundreds to thousands of concurrent sessions, and reduces flaky environment state compared with a fixed physical grid.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:40Outline
- 2:46Some background...
- 3:11Multiple machines
- 3:33Classic Grid ("farm")
- 4:41Something a bit different..
- 5:51What's wrong?
- 8:03Problems so far
- 10:22What we achieve in Google
- 11:43First attempt
- 14:05Second attempt: Architecture
- 21:57Other concerns
- 23:42Conclusion
related talks
44mReliable. Scalable. fast. Running 1000000 Android tests with Selenoid
34mUsing Selenium to Improve a Team's Development Cycle
47mWhat I Learned Building a Mobile Testing Infrastructure
10mPipe dream or reality? Mobile web testing in your CI/CD pipeline
39mTuesday Closing Keynote
40mScaling Selenium to infinity using AWS Lambda
21mThe Web has evolved. Has your testing evolved too?
09mTest Time Execution! Why it Can't be Ignored?