E2E2U: Slack’s journey to developer-driven end-to-end testing
summary
Slack migrates its black‑box Calabash suite to Espresso migration, converting ~100 slow E2E tests down to ~80 stable ones and integrating them as merge‑blocking checks. Tests adopt the robot pattern for readable, chainable flows, synchronize with app threads via Espresso idling resources and wrapped executors, run on Flank + Firebase Test Lab, and target a minified staging variant (workaround for ProGuard/R8). Result: ~7× speedup (41m → ~6m for some suites), ~83 E2E tests, $1.75 per full run, and developer ownership.
AI-written summary · about
chapters (5)
- 0:00Introduction and background
- 10:50Calabash challenges and issues
- 22:29Migrating to Espresso and robots
- 31:18Stabilizing end-to-end tests
- 38:50Current state and future plans
related talks
36mMobile performance testing at Slack
43mUI testing is so easy - said no developer ever
43mUI testing is so easy - said no developer ever
42mRock-Solid UI and Instrumentation Testing
08mAdaptation of the E2E Tests for a Big Project
45mMaintaining E2E Test Automation as We Transition from View…
29mHow to Shorten UI Test Run Times
32mBetter Integration Tests for Performance Monitoring