Maintaining E2E Test Automation as We Transition from View…
summary
Mercari payment features run on a one‑week release cycle with ~22.6M monthly users, ~254B JPY GMV, ~40 Android engineers and 100+ PRs/week, so automated E2E is mandatory. Implementation uses Espresso, Compose testing library, Firebase Test Lab + Flank, and TestRail; migration uses feature flag provider + Dagger Hilt, a page object model with Android View and Compose implementations, plus fake flags in tests. Practical gotchas: TestTag vs text confusion, subcomposition duplicate nodes, and waitUntil fixes; approach keeps tests maintainable and runnable in CI.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08Merpay app overview
- 10:27Current views and Compose
- 11:32Instrumented view tests
- 15:21Testing Compose screens
- 20:08Page Object Model
- 24:40Migrating tests to Compose
- 33:00QA and engineering collaboration
- 35:51E2E testing best practices
- 43:07Conclusion
related talks
37mState of Android Testing in 2022
43mUI testing is so easy - said no developer ever
42mProduction Level Test Driven Development and What's new
35mModern Testing on Android
17mYour E2E Tests Are Lying to You
29mTransformation Journey of E2E Customer Flow Testing...
44mE2E2U: Slack’s journey to developer-driven end-to-end testing
56mTesting for Success in the Real World