Reliable. Scalable. fast. Running 1000000 Android tests with Selenoid
summary
Claim: a Selenium-compatible cluster runs millions of Android tests by launching emulators in containers and scaling across data centers. Implementation uses Selenoid, Appium, ChromeDriver, ADB and Docker images with Android emulators and Android quick boot snapshots. A single cluster example runs >5,000 parallel browsers and ~2 million sessions per day, with cold-boot sessions ~30–40s reduced to ~5–10s with snapshots and typical test ~24s. Orchestration uses docker-compose, nginx/ggr load balancing and per-test container lifecycle to keep the fleet reliable and reproducible.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:46About me
- 1:24Selenium dusters
- 1:59Available browsers
- 3:15How about using real devices?
- 3:30What can differ between devices
- 3:56Typical device problems
- 4:37Real devices are a nightmare
- 4:55How Selenium works on desktop
- 5:28Android Debugging Bridge
- 5:52Android Emulator
- 6:45Android Instrumentation Framework
- 7:44Chromedriver
- 17:50Android Automation: Take #4
- 21:35Android Automation: Take #5
- 23:48Selenium Hub + Docker + Emulators
- 24:38How it should work
- 25:45Container start time
- 26:26Android Quick Boot
- 27:29Ready to use Android images
- 28:34Custom Android skin
- 29:04One Android server
- 29:36Android Cluster
- 35:56References
related talks
37mSelenoid Infrastructure: How to Run 1,000,000 Android Tests in Parallel
47mOreo, Nougat, Marshmallow and Lollipop: Effective Android Testing in 2019
31mScalable Selenium Cluster: Up & Running
41mDevice Server for an Android Farm or Running More Than 30k Tests Every Day
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
44mSelenoid: Ditch Selenium Server! Part 2
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem
43mSelenoid: running Selenium tests in Docker containers