Managing your UI tests simply and effectively
summary
Leboncoin presents a concrete Android UI testing pipeline using Barista (a wrapper around Espresso) for simpler assertions, Swarmer to launch and manage about 80 emulators in parallel, and Composer to orchestrate runs and produce human-readable reports. The setup runs in CI, captures screenshots, surfaces failures, reduces visual regressions, and is demonstrated on ~30 UI tests (most pass; one flaky test succeeds about 1 in 6 times).
AI-written summary · about
chapters (16)
- 0:00Start
- 0:49Leboncoin
- 1:36Our Continuous Integration Chain
- 4:27Houston, we've had a problem
- 5:21Our Needs
- 5:57Instrumentation - Android Emulator
- 6:13Instrumentation - Swarmer
- 6:31Test Orchestration - Spoon
- 6:52Test Orchestration - Composer
- 7:21Swarmer Instead of Android Emulator
- 9:32Composer Instead of Spoon
- 11:09Barista
- 11:59Comparison
- 13:00A Little Magic!
- 16:55And Then?
- 22:58Further Reading
related talks
44mEfficient testing UI Android apps by example
33mAndroid UI Testing & Challenges
42mRock-Solid UI and Instrumentation Testing
42mEfficient UI testing in Android
43mUI testing is so easy - said no developer ever
44mDrink Espresso during Android Testing
38mThe Testing Pyramid – What does it mean for Android?
49mSolving the Problems of Espresso Android Autotests in the Real World