Zero to hero in UI testing
summary
Explains a concrete recipe: use Espresso as the test engine, mock external dependencies so UI tests are hermetic, and start with OkReplay or a packaged MockWebServer with dispatcher for predictable responses. Build a small DSL of given/when/then steps so tests stay readable and reusable, run ~600 tests sharded across devices with Fork to hit CI (full suite ~25 minutes on 10 devices), reduce flakiness with Test Butler, idling resources and real-device mini farms, and keep a tiny end‑to‑end suite against production. Espresso + OkReplay MockWebServer with dispatcher Fork sharding
AI-written summary · about
chapters (12)
- 0:00Introduction and overview
- 1:29Testing pyramid explained
- 5:21Why developers avoid UI tests
- 8:06Writing first UI test with Espresso
- 10:57Mocking external dependencies
- 13:25Network layer mocking options
- 16:57Creating test DSL for cleaner code
- 21:49Benefits of behavioral tests
- 23:13Running tests in CI pipeline
- 27:02Common sources of test flakiness
- 34:04Scaling and maintaining tests
- 35:29Q&A session
related talks
42mRock-Solid UI and Instrumentation Testing
44mEfficient testing UI Android apps by example
43mUI testing is so easy - said no developer ever
46mEfficient Android UI Testing
29mHow to Shorten UI Test Run Times
56mTesting for Success in the Real World
53mSolving Espresso Android Autotest Issues in the Real World
43mUI testing is so easy - said no developer ever