Sneak Peek at the Screenshot Testing Landscape in 2024
summary
Compares six real tools (Paparazzi, Roborazzi, Compose Preview, Shot, Drop, Android Testify) with concrete tradeoffs: Paparazzi vs Roborazzi require AGP or Robolectric quirks, Compose Preview auto-generates screenshots from previews but needs a new test source, Shot has the nicest HTML reports, Drop and Testify offer Studio integration quirks. Claims instrumentation gives highest fidelity while JVM is much faster and less flaky (95% fidelity claim). Provides a cross-library utils plus a runnable repo Android Screenshot Testing Playground (Google OSS peer bonus 2024).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:11Screenshot testing workflow
- 3:58Compose preview tools
- 5:42Library configurations
- 7:28Instrumentation screenshot comparison
- 9:56JVM screenshot comparison
- 13:29Choosing library type
- 14:30Cross-library solutions
- 15:33Screenshot testing problems
- 17:17Solutions for screenshot issues
related talks
35mEasy screenshot testing with Compose
38mMastering Screenshot Testing for Android Apps
18mScreenshot testing – The practical talk
01h 28mMastering Screenshot Testing Libraries for Android: A Hands-On Workshop
44mAutomating Screenshot Testing in Compose Multiplatform
37mSnapshot testing (and more!) with Paparazzi
41mAndroid Screenshot Testing on Autopilot
23mAll your Compose @Previews to screenshot tests without instrumentation