Making your Espresso sweeter
summary
Explains a concrete rework: raw Espresso tests with 37 lines and many imports get refactored into Page Object pattern page classes, then a shared harness library that centralizes execute(action) and logging, reducing a test to 19 lines and dropping three import lines per page. Network calls get recorded and replayed with OKReplay, cutting flaky, environment-dependent failures and speeding runs from seconds to milliseconds variability. Internal libraries share the same API across three Android apps and an equivalent iOS suite.
AI-written summary · about
chapters (12)
- 0:00Introduction to UI testing
- 1:52Basic Espresso test structure
- 3:57Problems with raw Espresso tests
- 4:39Page object pattern explained
- 6:43Refactoring with page objects
- 8:28JUnit dependency issues
- 9:31Espresso internals and limitations
- 11:16Centralizing test execution
- 13:41Maintenance burden reduction
- 14:24Mocking API dependencies
- 16:10Cross-platform test consistency
- 17:12Q&A session begins
related talks
49mSolving the Problems of Espresso Android Autotests in the Real World
38mEspresso, beyond the basics
42mRock-Solid UI and Instrumentation Testing
43mUI testing is so easy - said no developer ever
37mEspresso Patronum: The Magic Of The Robot Pattern
56mEspresso is Awesome!
53mSolving Espresso Android Autotest Issues in the Real World
42mZero to hero in UI testing