Espresso, beyond the basics
summary
Explains how Espresso actually synchronizes: analysis of activity lifecycle monitor, UIController and idle resources, and why a suite of 800 automated tests needs explicit threading hooks. Shows a practical pattern of wrapping ExecutorService (and analogous RxJava schedulers) to register idling counters, how events reach InputManager, and how ActivityTestRule/TestRule let rules take screenshots on failure. Notes tooling: Espresso Test Orchestrator, multi‑process support, and using Gradle to install test helpers.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:40Espresso
- 4:00Dependencies
- 13:08Synchronization
- 14:01Actions
- 16:53Idle Resource
- 19:52Wrapping Executor Service
- 23:57Idle from a Square
- 25:15Design well
- 26:41Functionality
- 27:33Test Roles
- 30:33Rule Chain
- 31:39Operations
- 32:44Orchestrator
- 35:20Multiprocess Espresso
related talks
36mHow Espresso Works
57mHow Espresso Works
44mDrink Espresso during Android Testing
01h 29mHello Espresso! Start with Android Gray box automation
42mRock-Solid UI and Instrumentation Testing
53mSolving Espresso Android Autotest Issues in the Real World
56mEspresso is Awesome!
44mTaking care of your UI tests