Visual regression test with cypress
This tool was created to make visual regression as simple as possible, by exposing basic functions that allow you to view the difference between images. The wrapper uses pixelmatch which is simple and powerful and relies on cypress to take screenshots.
Once you have setup cypress and followed Cypress integration you can start writing tests
Create a spec file under cypress integration folder i.e cypress/integration/specs/some-test-spec.js
Then use the cypress image diff command to take screenshots of pages or elements:
describe('Visuals', () => {
it('should compare screenshot of the entire page', () => {
cy.visit('www.google.com')
cy.compareSnapshot('home-page')
})
})
You can also make the comparison assertion more flexible by applying a higher threshold (default is 0):
describe('Visuals', () => {
it('should compare screenshot of the entire page', () => {
cy.visit('www.google.com')
cy.compareSnapshot('home-page-with-threshold', 0.2)
})
})
You can also retry the snapshot comparison by passing in an optional third parameter. It accepts the same options as cypress-recurse.
describe('Visuals', () => {
it('should compare screenshot of the entire page', () => {
cy.visit('www.google.com')
const retryOptions = {
limit: 5, // max number of retries
delay: 500 // delay before next iteration, ms
}
cy.compareSnapshot('home-page-with-threshold', 0, retryOptions)
})
})
describe('Visuals', () => {
it('should compare screenshot from a given element', () => {
cy.visit('www.google.com')
cy.get('#report-header').compareSnapshot('search-bar-element')
})
})
describe('Visuals', () => {
it('should compare screenshot from a given element', () => {
cy.visit('www.google.com')
cy.get('#report-header').hideElement() // hideElement(false) to unhide
cy.compareSnapshot('search-bar-element')
})
})
If there are wanted changes to the application in test and if we need to update baseline images, you can follow the steps in CLI documentation to update the baselines.
Alternatively you can delete the baseline image that you wish to be updated and rerun the tests, this will create a new baseline image with the updated image.
Folder structure is hard coded (see below). There will be enhancements coming in to make it configurable:
.
├── cypress-visual-screenshots
├── baseline
├── comparison
├── diff
In order to force the screenshot resolution when running a test you will need to set the following cypress config values in cypress.json
:
{
"viewportWidth": 1000, // Default value: 1280
"viewportHeight": 660 // Default value: 720
}
All screenshots will be renamed and moved from the default screenshot location to a new screenshot folder structure. To preserve the screenshot in the original location, set the following values in cypress.json
:
{
"env": {
"preserveOriginalScreenshot": true
}
}
Be aware that despite forcing a screenshot resolution to a particular height and width for a test, if this test is run on different computers (i.e a 13" Mac vs PC attached to a 30" monitor), the results will be different. So it's extremely important that you standardize where the tests will run, both locally and CI.
One way to handle this is by running it with docker container. This project tests use a docker container to run the tests so it could be used as an example.