UI testing is so easy - said no developer ever
summary
Slack proves reliable Android UI testing at scale by making tests targeted and hermetic and automating state setup. They run 555 functional UI tests, use Espresso + Mockito + Dagger + AutoValue, and replace bulky mock setup with mirror “power‑pack” classes that build model state (users, channels, messages) so tests just call addUser/addChannel. Developer survey ease of testing rises from 2.5/4. Future plan: auto-generate packs by replay API traffic captured from end-to-end suites.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:38Why UI testing
- 1:21Surveys
- 3:08No time
- 4:47Google Wallet
- 7:22Robot IAM
- 8:35Espresso
- 10:14New API
- 11:02Double Espresso
- 12:30Android Testing Support
- 13:00UI Testing Presentation
- 13:40Android Testing Support Logo
- 14:01Slack Android UI Testing
- 16:28Inverted UI Testing Pyramid
- 17:17Practical Guide to UI Testing
- 18:20Why we are here
- 18:49UI tests
- 19:46Survey results
- 20:40Testing robots
- 21:04MVP pattern
- 22:31Test hackathon
- 24:04The problem with robots
- 28:00The solution
- 29:17Starter pack
- 31:08API
- 35:12Test doubles
- 39:38Better solution
related talks
46mEfficient Android UI Testing
44mEfficient testing UI Android apps by example
38mThe Testing Pyramid – What does it mean for Android?
23mManaging your UI tests simply and effectively
42mRock-Solid UI and Instrumentation Testing
33mAndroid UI Testing & Challenges
53mSolving Espresso Android Autotest Issues in the Real World
42mEfficient UI testing in Android