Espresso: A Screenshot is Worth 1,000 Words
summary
Uses Espresso to take programmatic screenshots and attach them to Spoon HTML reports so CI and non-developers see exactly what tests exercise; uses the Robot pattern so each robot action automatically captures a named screenshot making screenshots effectively free and a single update to a robot fixes many tests. Compares screenshot backends (Falcon adds ~16% runtime, UI Automator gives prettier images but much higher cost), recommends screenshots-on-failure, mock data for Tesla‑like speed, Test Butler to disable animations, and sharding for parallel CI.
AI-written summary · about
chapters (10)
- 0:00Introduction to talk
- 1:23What is Espresso
- 4:51Why take screenshots
- 9:27Spoon test runner demo
- 12:36Screenshot libraries compared
- 17:52Performance overhead of screenshots
- 20:21Maintainable test architecture
- 26:18Tips and tricks for Espresso
- 33:14How to get started
- 36:29Q&A session
related talks
56mEspresso is Awesome!
38mEspresso, beyond the basics
53mSolving Espresso Android Autotest Issues in the Real World
49mSolving the Problems of Espresso Android Autotests in the Real World
19mTesting Beyond Unit
44mEfficient testing UI Android apps by example
31mFurther Speeding Up UI Tests (Espresso)
44mDrink Espresso during Android Testing