The Android Device Farm That Fits in a (Cloudy) Pocket
summary
A pocketable device farm called Poddingue wires real Android devices into OpenSTF using Docker, HypriotOS, Armbian and GitLab CI so CI jobs can reserve devices via API and run tests remotely. Providers run on Raspberry Pi and other low‑cost SBCs, builds use QEMU/emulation to produce ARM images, and a single master can manage up to 49 attached devices, with some ARM ports and touchscreen work still in progress.
AI-written summary · about
chapters (17)
- 0:00Android fragmentation
- 1:01Virtual vs hardware tests
- 3:51Poddingue solution
- 5:13Open STF remote tests
- 8:45Master-slave architecture
- 11:11Farm limits and risks
- 13:18Reservation workflow
- 15:05Device security and booking
- 17:12Raspberry Pi experiments
- 21:05ARM compilation fixes
- 25:38Compatibility patches
- 28:06SBC cards specifics
- 31:37Hardware optimization
- 35:12Poddingue goals
- 37:58Enterprise farm steps
- 39:47Quick start with Pi
- 40:50Q&A
related talks
41mThe Android device farm that fits in a cloudy pocket
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem
41mDevice Server for an Android Farm or Running More Than 30k Tests Every Day
29mPros and Cons of Device Farms Available for Android
14mMobile Farming for Perfection
38mMobile Device Farms Demystifying Testing Strategies Between Theory and Real World Practice - Sergio
46mDockerization of a real mobile device farm and scalable QA automation
39mOverview of Device Farms for Mobile Testing