Visual Version History
summary
Proposes visual version control: take screenshots on every commit using a headless browser, store them in a git submodule, and script interactions with RSpec to capture pages and individual components. Claims this prevents accidental UI regressions and creates a private wayback machine for each screen. Notes practical problems: component-wide changes create noise so capture isolated components and compute a numeric diff like root mean square distance to rank visual change. Mentions tooling: huxley and github image div.
AI-written summary · about
chapters (8)
- 0:00UI Testing
- 0:18Deployment
- 0:38Screenshot
- 0:55Version Control
- 1:22Big Words
- 2:00Useful Tips
- 3:02Tools
- 3:21Huxley
related talks
18mImplementing a Visual CSS Testing Framework
28m"Git hook[ed]” on images & up your documentation game
27mVisual UI Testing – Testing the Last Mile
09mTelling stories through your commits
09mMicro-Versioning Tool to Support Experimentation in Exploratory Programming
54mVisual Validation
58mUnit Testing with Screenshots: Breaking the Sound Barrier
12mIntegrating visual testing into the build pipeline