How Espresso Works
summary
Explains precise mechanics: Espresso wires objects with Dagger 2, builds a ViewInteraction, then synchronizes by copying the idling registry into internal state and calling loopMainThreadUntilIdle which runs a main‑thread interrogation that even uses reflection into MessageQueue to pull and dispatch pending messages. View matching uses Hamcrest matchers and throws specific exceptions for no match or ambiguous matches; matches(isDisplayed) checks globalVisibleRect and effective visibility. Activity launches use ActivityTestRule and startActivitySync with a built‑in 45 second timeout.
AI-written summary · about
chapters (4)
related talks
36mHow Espresso Works
38mEspresso, beyond the basics
44mDrink Espresso during Android Testing
01h 29mHello Espresso! Start with Android Gray box automation
26mEspresso Patronum - The Magic Of The Robot Pattern
53mSolving Espresso Android Autotest Issues in the Real World
43mUnlocking New Testing Capabilities with Espresso Driver
42mRock-Solid UI and Instrumentation Testing