As you know, to have automated visual regression tests (in addition to unit and integration tests) is important to ensure the users a good experience.
This assures that nothing is accidentally broken and confirms that user flows and the appearance of your application are functional when the existing code is modified or a dependency is updated.
Recently, I wrote an article on visual regression testing with TypeScript, Jest, Jest Image Snapshot and Puppeteer. If you use Puppeteer, you know that you can test only under Chromium. The implementation with Firefox is experimental, and Webkit is not supported at all. Today…
As developers, it is our job to ensure that our users get an experience with no regression.
Like any good developer, when I add a feature or fix a bug, I also create unit, integration, and end-to-end tests. This assures that, when the existing code is modified, nothing is accidentally broken, and confirms that user flows are functional.
Like many people, I’ve gotten used to using a manual process to visually check that the design looks as intended.
Refactoring, adding a new component, or updating a package can sometimes change the appearance of the application. It can get laborious to…