Where and how to run UI tests?
summary
Clear recommendations and measured tradeoffs: marathon is the most capable open‑source runner here, with retries, device-aware reruns and adb replacements to reduce overhead; replacing physical devices with Docker emulators cuts average test time from ~50s to ~30s per test; using Android Test Orchestrator forces extra APK installs and adds up to ~12s gaps per isolation cycle; network record‑and‑replay (WireMock/OkReplay style) stabilizes tests; paid cloud runners like flank (≈$5/device‑hour) avoid infra work but cost more at scale.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:03First implementation
- 2:29Check the junctions
- 4:15What affects quality?
- 16:19It's complicated
- 20:052. Speed problems
- 20:48Tooling
- 21:39Flakiness protection levels
- 24:30Marathon vision
- 32:26Difference
- 33:06Flank vision
- 35:14Real device
- 38:09How to build emulator?
- 38:41Docker emulators
- 40:41Dedicated stage
related talks
34mSetting up Android UI Testing on CI
46mEfficient Android UI Testing
29mHow to Shorten UI Test Run Times
23mManaging your UI tests simply and effectively
26mAndroid CI: 2016 edition
45mParallel testing of Android UI on a large scale
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
43mAndroid Apps Testing in 2019