Visual regression testing: your strategy's blind spot
summary
All green tests still miss pixel bugs so screenshot testing catches visual regressions that functional tests never see, demonstrated by a translator app where a color change from red to blue breaks UI expectations but not logic. The demo uses WireMock+Maestro+ImageMagick to fake servers, drive the UI, crop system bars and produce baseline, actual and diff directories, stores baselines in a Cloudflare/S3 bucket, and flags diffs in CI; it works but requires nontrivial setup and flakiness handling.
AI-written summary · about
chapters (12)
- 0:00Testing blind spot
- 5:03Testing pyramid limits
- 6:48Visual regression testing
- 8:14Benefits of visual testing
- 10:23Implementing visual tests
- 13:12Baseline storage pitfalls
- 17:29Emulators vs device farms
- 20:17Deterministic screenshots
- 22:44Demo setup with WireMock
- 28:06Running the demo
- 32:40Wrap-up advice
- 35:52Q&A
related talks
37mThe Colorful World of Visual Test Automation
27mVisual UI Testing – Testing the Last Mile
53mPainless visual testing
20mVisual testing with Visual Regression Tracker
12mAutomation of GUI testing using visual regression testing
39mSpot the difference: automating visual regression testing
43mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
21mVisual Regression Testing: From a Tool to a Process
