Pre-submit UI Tests at Pinterest
Article Summary
Pinterest's UI test suite was failing more than 50% of the time. Engineers were drowning in false positives, and tests had lost all credibility.
Pinterest's mobile team moved their entire end-to-end UI test suite from post-submit to pre-submit, running 300 tests on every code change. This meant solving hard problems around speed, cost, flakiness, and developer experience.
Key Takeaways
- Pass rate jumped from under 50% to over 90% after the shift
- Every test requires an owner and silenced tests must be fixed within 2 weeks
- Smart sharding and custom schedulers keep 300 tests under 30 minutes
- Result caching lets devs skip reruns when tests are false negatives
- Stability Enforcer auto-silences tests showing over 20% flakiness
Critical Insight
By running UI tests before merge instead of after, Pinterest cut investigation time, raised pass rates to 90%, and made their test platform actually trustworthy again.