Mastering the mobile testing pyramid
summary
Argues that success starts by make app automatable: add debug menus/backdoors and turn off AB tests so pre-release builds show deterministic states, then automate tests that treat the UI as a black box. Tests must be repeatable deterministic isolated (avoid creating accounts that block later runs). Recommend selective end-to-end runs: fast PR suites under 20 minutes, fuller main-branch checks, and exhaustive beta runs. Demonstrates these practices using Waldo, a browser‑based mobile E2E orchestration platform, and reports reduced flakiness and maintenance.
AI-written summary · about
chapters (10)
- 0:00Introduction to mobile testing
- 1:54The testing pyramid explained
- 5:00Struggles of mobile testing
- 6:44Mindset shift for automation
- 8:08Automate your app first
- 12:18Decoupling implementation and testing
- 15:06Repeatable deterministic isolated tests
- 17:32Building a testing strategy
- 22:46Benefits of proper testing
- 23:27Q&A and closing
related talks
23mWhy testing is also a developer's problem
56mTesting for Success in the Real World
55mShifting the Testing Role Pendulum
44mEfficient testing UI Android apps by example
32mWhy testing is a developer's problem
38mFlipping the Testing Pyramid
46mTowards Joyful Development
18mExploration of tools, frameworks to take the pain out of mobile app testing!