The device is running on it's own! Full-stack automation of UI testing on a custom android firmware.
summary
A custom Karoo bike computer running a forked Marshmallow Android gets full CI/CD UI testing: an orchestrator app auto-downloads and installs OTA ROMs, runs tests across bundled APKs and uploads results to Jenkins pipeline mapped to commit hashes. Test suite has >70% unit coverage, a homegrown DSL abstraction unifies Espresso and UIAutomator, and one always-on device performs nightly builds for a two-week release cadence. The setup works but teams keep a final manual gate because not everything safely automates.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 0:26Introducing the Karoo device
- 2:32Custom Android firmware architecture
- 4:38Inter-app communication methods
- 6:02Microservice-like service structure
- 7:24Testing challenges on custom firmware
- 8:46Manual testing limitations
- 10:11Solution: Orchestrator app
- 11:56Automation device setup
- 12:41CI/CD pipeline integration
- 13:43Nightly build and monitoring
- 14:04Key learnings and conclusion
related talks
30mAutoMobile
26mAndroid CI: 2016 edition
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
23mManaging your UI tests simply and effectively
43mUI testing is so easy - said no developer ever
53mCI for Android Using Jenkins
42mSupercharging Android Testing: Scalable Environments for Larg…