4 ms·
I've found testing tools that take screenshots very useful. Once you're happy with the site, you take screenshots at various screen widths and after you make ch
by seanwilson 9y ago
I've found testing tools that take screenshots very useful. Once you're happy with the site, you take screenshots at various screen widths and after you make changes you can view visual diffs of the new screenshots to see if you broke anything.
- erichurkman 9y agoWe've had good luck with Percy. It was a few lines of code to have it drop HTML+static assets to them, they take care of screen shots. It takes screen shots (HTML) via our normal test suite, so we didn't have to write any new tests. It shows up as a check on every merge request we have from develop->master, and any visual differences get a manual check. It works great, even on large refactors!
- seanwilson 9y agoDo you have to pay to use that? If so do you find it restricts you? Sounds like something you want to self-host. I've used Wraith before which works OK but their version of PhantomJS is pretty old.
- erichurkman 9y agoYeah, we pay. And no. The benefit is they take care of rendering, our test suite only has to send DOM (html) snapshots with static assets. We, in turn, get a consistent rendering environment that can rapidly render+diff 100s++ screen shots in a minute or two. The key benefit is that it doesn't take our test suite much additional time to do it since our side is lightweight.