Drink Espresso during Android Testing
summary
Kotlin examples show UI tests written with Espresso (API level 8, covers ~100% active devices) plus occasional UI Automator for cross-app flows and notifications; tests use ActivityTestRule with auto-launch=false to start from specific screens, custom matchers for snackbars and list items, RecyclerView actions, and rule chains to order setup. Synchronization relies on IdlingResource or CountingIdlingResource, plus disabling app animations via global settings; combination of tools reduces flakiness and runs on devices/emulators (UI Automator requires min API 18).
AI-written summary · about
chapters (15)
- 0:00Introduction
- 6:04Android Testing Support Library
- 7:28GUnit Rules
- 11:05Espresso
- 13:13View Interaction
- 17:30List
- 25:00Test Activities
- 28:07UI Automator Viewer
- 29:02Testing Support Library
- 30:09Testing Calculator Application
- 30:43Testing Calculator App
- 32:57UI Automator
- 34:01Conclusion
- 37:35UIAutomator
- 39:16API
related talks
01h 29mHello Espresso! Start with Android Gray box automation
53mSolving Espresso Android Autotest Issues in the Real World
33mAndroid UI Testing & Challenges
44mEfficient testing UI Android apps by example
42mRock-Solid UI and Instrumentation Testing
46mEfficient Android UI Testing
38mEspresso, beyond the basics
43mAndroid Apps Testing in 2019