Easy screenshot testing with Compose
summary
Screenshot testing verifies visuals by comparing new images to golden files and the ecosystem now supports JVM rendering with tools like Roborazzi and Paparazzi and device runs via Shot/Dropshots; Robolectric/layoutlib enable fast local checks and CI produces deterministic baselines. Practical guidance includes the 50KB average, 1,000 files → 50MB storage example and options like Git LFS or external buckets, automating record vs verify and bot commits on CI. Android Studio adds a preview-based Studio feature that converts previews into tests (command‑line first), and adopters report ~30% more IDE testing and billions of screenshot tests per month run.
AI-written summary · about
chapters (8)
- 0:00Introduction to screenshot testing
- 1:08What is screenshot testing
- 7:57Why screenshot testing now
- 15:30Obstacles and considerations
- 21:55Managing screenshot files
- 27:13Platform differences and solutions
- 30:02New Android Studio feature
- 34:58Summary and next steps
related talks
19mSneak Peek at the Screenshot Testing Landscape in 2024
44mAutomating Screenshot Testing in Compose Multiplatform
38mMastering Screenshot Testing for Android Apps
01h 28mMastering Screenshot Testing Libraries for Android: A Hands-On Workshop
42mMaking UI Specs Visible — Compose Screenshot Testing and a Gallery to Support the AI Agent Era
40mUnderstand the mechanism! Screenshot-testing Compose previews in many variations
41mAndroid Screenshot Testing on Autopilot
23mAll your Compose @Previews to screenshot tests without instrumentation