Selenoid Infrastructure: How to Run 1,000,000 Android Tests in Parallel
summary
Selenoid runs Android emulators as one-emulator-per-Docker-container using ADB inside each container and quick-boot snapshots to reduce cold start time from ~30–40s to ~5–10s. It ships ready images containing Appium, ChromeDriver, and the Android SDK, scales by hosting ~30 emulators per powerful machine, and balances load across data centers via a grid router to support thousands of requests per second and millions of sessions per day.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:06Selenoid cluster scope
- 2:30Real Android devices
- 3:58Automation challenges
- 5:45Scalable automation
- 6:06Selenium desktop
- 6:49Android automation
- 9:35OpenSTF for automation
- 11:00Installing Selenoid
- 14:08Running emulator test
- 15:32Debugging with UI
- 16:35Changing device
- 17:39Recording execution
- 19:38Emulator issues on VMs
- 22:27Scaling with Docker
- 25:35Optimizing setup
- 27:01Selenoid vs Selenium
- 27:45Slow emulator startup
- 28:28Quick Boot solution
- 29:09Android images in Selenoid
- 30:53Production server
- 31:34Scaling cluster
- 33:18Summary
related talks
44mReliable. Scalable. fast. Running 1000000 Android tests with Selenoid
47mOreo, Nougat, Marshmallow and Lollipop: Effective Android Testing in 2019
41mDevice Server for an Android Farm or Running More Than 30k Tests Every Day
34mRun your Appium tests using Docker-Android
43mSelenoid: running Selenium tests in Docker containers
23mAppium Dockerization – From Scratch to Advanced Implementation
28mAppium meets Selenium and Docker
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem
