Screenshot testing – The practical talk
summary
Evaluates Shot and Dropbox (emulator-based) and Paparazzi; finds none perfect. Shot/Dropbox (emulator-based, sensitive to device/DPI/OS differences) requires identical emulators and fails on M1 vs x86 text/color rendering. Paparazzi (no emulator, unit tests, fast) runs as JVM tests, supports parameterized day/night and devices, uses Record/Verify on CI, stores PNGs in a snapshot folder and recommends Git LFS; 40 tests (80 images) run in ~26s. Notes Paparazzi quirks: TextInputEditText, ConstraintLayout full-height, missing button rendering, and occasional layout preview drift.
AI-written summary · about
chapters (12)
- 0:00Introduction to screenshot testing
- 1:16Problem and motivation
- 4:02Evaluating screenshot testing libraries
- 6:31Challenges with emulator-based testing
- 8:17Switching to Paparazzi
- 9:40Writing screenshot tests with Paparazzi
- 11:07Configuring tests and CI
- 12:51Debugging and verifying screenshots
- 14:16Performance and speed benefits
- 15:38Designer collaboration and workflow
- 16:42Limitations and issues with Paparazzi
- 17:22Future of screenshot testing
related talks
37mSnapshot testing (and more!) with Paparazzi
19mSneak Peek at the Screenshot Testing Landscape in 2024
35mSnapshot testing (and more!) with Paparazzi
01h 28mMastering Screenshot Testing Libraries for Android: A Hands-On Workshop
33mKeeping your Pixels Perfect �: Paparazzi 1.0
35mEasy screenshot testing with Compose
35mLights, Camera, Snapshot! What’s New in Paparazzi 2.0
31mAn Introduction to Effective Snapshot Testing on Android