Solving Espresso Android Autotest Issues in the Real World
summary
Describes using Espresso for fast, in-app Android UI tests and building a Kotlin DSL over ViewActions to make tests readable. Covers running 500 tests in parallel across 5 devices, a debug-only IdlingResource wrapper for long backend loads, retry/filtering to detect and exclude flaky tests, and integrating Allure reporting (screenshots and dumps); provides a demo app and reusable GitHub library and reports reduced noise and faster feedback.
AI-written summary · about
chapters (19)
- 0:00Android testing intro
- 1:23Espresso vs UI Automator
- 3:55Why Espresso is faster
- 5:59White-box testing benefits
- 8:04Espresso for large projects
- 10:11Readability issues
- 13:23Custom Espresso DSL
- 19:49DSL for readable tests
- 21:13Test stability and waits
- 23:05IdlingResource for sync
- 29:48IdlingResource without app changes
- 34:25IdlingResource in production
- 36:18Flaky tests and devices
- 38:08Fighting flakiness with Flank
- 41:17Test usefulness
- 42:21Speeding up with parallel runs
- 43:45Allure reports
- 46:41Tests bringing value
- 47:36Q&A
related talks
49mSolving the Problems of Espresso Android Autotests in the Real World
44mDrink Espresso during Android Testing
44mEfficient testing UI Android apps by example
33mAndroid UI Testing & Challenges
44mTaking care of your UI tests
01h 29mHello Espresso! Start with Android Gray box automation
46mEfficient Android UI Testing
42mRock-Solid UI and Instrumentation Testing