Setting up Android UI Testing on CI
summary
Runs a 250-test UI suite at ~4s per test (≈17 minutes) and concludes that neither PR-only nor nightly-only scheduling works without classifying tests by scope and impact. Explains device choices: emulators are cheap and scalable, real devices are realistic but costly, Docker containers scale but are hard to set up. Recommends sharding across devices, idling resources instead of Thread.sleep, retry strategies for flakiness, and using Flank or Marathon with Firebase Test Lab for reporting, videos and pooling.
AI-written summary · about
chapters (8)
- 0:00Introduction to UI testing
- 1:27Integration with CI tools
- 6:01Preparing Android environment
- 8:30Choosing test execution devices
- 15:56Optimizing test execution
- 23:20Handling flaky tests
- 27:18Using test runners
- 31:07Summary and key takeaways
