Testing Beyond Unit
summary
Compares Espresso UI checks with Facebook’s open‑source screenshot-tests-for-android and argues for storing baseline images and running CI pixel‑by‑pixel diffs to catch subtle visual regressions. Shows how to render deterministic bitmaps, set fixed layout sizes, and capture RTL and force‑dark variants. Recommends capturing screenshots on test failures and during E2E steps so diffs appear on pull requests, and notes tradeoffs: test churn when UI intentionally changes and the option to use thresholds instead of strict pixel equality.
AI-written summary · about
chapters (8)
- 0:00Introduction to testing
- 2:14Espresso UI testing limits
- 4:17Screenshot testing benefits
- 6:31Setting up screenshot tests
- 8:19Testing RTL and dark mode
- 9:24Debugging with screenshots
- 10:09Documenting features visually
- 10:30Closing and Q&A
related talks
31mAn Introduction to Effective Snapshot Testing on Android
44mEfficient testing UI Android apps by example
43mMobile: Test Every Pixel - Screenshots in UI Tests (...)
35mEasy screenshot testing with Compose
46mFive Lessons from Implementing Pixel-Perfect Testing of a Design System on Android
41mSnapshot Testing with Native Mobile Frameworks
38mThe Testing Pyramid – What does it mean for Android?
58mUnit Testing with Screenshots: Breaking the Sound Barrier