What I Learned Building a Mobile Testing Infrastructure
summary
Built a full mobile test stack using Selenium/Appium, Docker, QEMU/VirtualBox and Prometheus monitoring, and documents concrete tradeoffs: infrastructure as code reduces manual VM drift, emulators boot in ~40–60s but need 3 CPUs and 3 GB RAM each, image combinatorics explode to 1700 images if every OS/browser/driver/version is kept, and moving from handcrafted VMs cut a suite from 1h15m to ~20m. Recommends prometheus for CPU/RAM sizing, mac minis for legal iOS hosts, and continuous maintenance and scoped resource planning.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:02Selenium
- 6:42Test the test environment
- 9:42My tests are slow...
- 11:46Setup Details
- 15:22Stack Layout
- 22:10Emulators Challenges
- 25:52Simulators Challenges
- 33:45Test the test infrastructure
- 39:00Quality Gate
- 40:11Price
- 42:51Thank you!
related talks
46mDockerization of a real mobile device farm and scalable QA automation
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
52mBuilding an Advanced Automation Solution Based on Appium
47mOreo, Nougat, Marshmallow and Lollipop: Effective Android Testing in 2019
25mBuilding a scalable device lab with Ansible
10mPipe dream or reality? Mobile web testing in your CI/CD pipeline
26mMobile Test Automation Frameworks – From the Basics to Usage