How to Shorten UI Test Run Times
summary
This talk compares slow Android UI tests (Espresso) to faster unit tests and shows how parallel sharding with Spoon across devices (via STF/Jenkins) cut wall-clock time but exposed data races and setup overhead. Concrete fixes include replacing sleeps with IdlingResource, pre-seeding test data, giving each shard its own test users, and skipping tests that can’t shard (e.g., chat), and the team is building a planner called Pomaranian to optimize shard assignment.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:04UI test times matter
- 8:49Long UI test problems
- 11:22Shortening test times
- 15:48Parallelization sharding
- 20:51Measuring speed gains
- 24:50Results challenges
- 27:19Future plans
related talks
31mFurther Speeding Up UI Tests (Espresso)
34mSetting up Android UI Testing on CI
33mAndroid UI Testing & Challenges
42mRock-Solid UI and Instrumentation Testing
42mEfficient UI testing in Android
38mThe Testing Pyramid – What does it mean for Android?
44mEfficient testing UI Android apps by example
46mEfficient Android UI Testing