Scale Up Your Snapshot Testing Without the Friction

on YouTube ↗29m

" summary

Snapshot testing at scale means generate images in CI to avoid ARM/Intel and OS drift, store heavy PNGs outside Git (a full-screen snapshot ≈ 50 KB per snapshot, so 1,000 ≈ 50 MB and 100 UI churns ≈ 5 GB), and accept that 99% intentional changes justify an “accept” workflow on PRs. Build artifacts or a hosted service (Screenshotbot is open source and offers PR statuses, Slack alerts, image zoom/diff, history with bisect, masking for animations) to cut flakiness and developer friction.

AI-written summary · about

" chapters (10)

1. 0:00Introduction to snapshot testing
2. 1:49Snapshot vs screenshot vs golden tests
3. 4:40Why teams abandon snapshot tests
4. 7:06Storage challenges in snapshot testing
5. 9:33Solutions to snapshot friction
6. 12:19Reducing intentional change friction
7. 15:07Screenshot Bot workflow demo
8. 16:52Better image comparison tools
9. 18:18Advanced Screenshot Bot features
10. 20:25Call to action and Q&A

" related talks

• 35mBuilding a screenshot testing pipeline that scalesLukas Appelhans · DroidKaigi 2023
• 35mEasy screenshot testing with ComposeJose Alcérreca · Droidcon London 2023
• 31mAn Introduction to Effective Snapshot Testing on AndroidSergio Sastre Flórez · droidcon Berlin 2021
• 58mUnit Testing with Screenshots: Breaking the Sound BarrierRoman Dvornov · HolyJS 2017
• 18mScreenshot testing – The practical talkBenedict Pregler · droidcon Berlin 2022
• 23mScreenshot testing with ViteShotFrançois Wouts · React Finland 2021
• 31mAutomating UX Compliance TestingDavid Tolley, Dima Kovalenko · Selenium Conference 2013
• 37mSnapshot testing (and more!) with PaparazziJohn Rodriguez · droidcon London 2022