UI Testing at Pinterest
summary
Pinterest runs a scaled UI test system that shrinks a six‑hour suite into commit‑time checks by moving to Firebase Test Lab with Flank sharding, using emulators (Nexus lowres), Espresso and Kotlin, and cutting runtime cost about 30% cost reduction. The infra handles ~17,000 builds and ~2.2M UI runs per month for ~30 developers, defines flakiness as inconsistent results, retries tests up to 2 retries (3 runs), enforces test ownership, provides Metro dashboards, Pin Tester and a login manager, and requires stabilization (e.g. 100‑run validation) before a test blocks commits.
AI-written summary · about
chapters (11)
- 0:00Introduction to UI testing
- 1:17History of UI testing at Pinterest
- 4:45Speeding up Android UI tests
- 6:32Defining and measuring test stability
- 9:40Core principles for UI testing
- 15:41Android technologies and tools
- 17:27Cross-platform testing tools at Pinterest
- 19:59Introducing Metro testing dashboard
- 27:49Metro features and dashboards
- 31:43Recommendations and next steps
- 37:28Q&A and closing remarks
related talks
44mRock-Solid UI and Instrumentation Testing
23mUI Testing for Fun and Profit
21mTasting Tests at Cookpad
34mSetting up Android UI Testing on CI
45mTesting the web without testers — success or failure
29mHow to Shorten UI Test Run Times
22mTwo years of UI Testing
26mEfficient Android Builds at Scale: Lessons from Pinterest
