npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cypress-looks-same

v2.0.1

Published

Cypress plugin for visual regression testing

Downloads

277

Readme

cypress-looks-same

A plugin to Cypress for visual regression testing, based on looks-same.

Getting Started

Start by installing the NPM package:

yarn add --dev cypress-looks-same

In your cypress/plugins/index.js file, add:

const addLooksSamePlugin = require('cypress-looks-same/plugin');

module.exports = (on, config) => {
    addLooksSamePlugin(on, config);
};

In your cypress/support/index.js file, add:

import addLooksSameCommands from 'cypress-looks-same/commands';

addLooksSameCommands();

Then in your tests, you can do this:

describe("stuff", () => {
    specify("element visuals", () => {
        cy.get('.my-element')
            .shouldLookSameAs('test image');
    });
});

The first time this runs, a cypress/snapshots/TestFile.spec.js/element visuals - test image.png file will be created. The next time it runs, another screenshot will be taken and compared to the existing snapshot.

If the screenshots look different, the assertion will fail and actual and diff files will be created next to the snapshot.

If the screenshots look the same, the assertion passes, and any actual and diff files are cleaned up. The original element is returned for chaining.

You can compare screenshots of the whole screen by not specifying a subject:

cy.shouldLookSameAs('whole screen');

Configuration

You can pass an options object in to shouldLookSameAs to customise the screenshot and image comparison:

cy.shouldLookSameAs('image', { /* ...options */ });

You can specify any of the options made available by the screenshot command or by looks-same.

Defaults

Rather than specifying the same options everywhere, you can set defaults by passing them in to the addLooksSameCommands() call in your support file.

Environment variables

Two environment variables are made available:

Variable | Description ---------------------------|------------ updateImageSnapshots | When set to true, snapshots will be updated instead of comparing against them. continueWhenLooksDifferent | When set to true, tests will continue running even when screenshots don't match existing snapshots. This makes it easy find all the mismatches in one run.

Extras

There is also a compareWithImageSnapshot command, which does the same thing as shouldLookSameAs, but returns the comparison results instead of asserting on them. The results have the following properties:

Property | Description ----------------|------------ imagesMatch | true if a snapshot exists and matches the new screenshot. false if the snapshot is updated, or it doesn't look the same. snapshotUpdated | true if the snapshot image was created or updated. snapshot | Path to the snapshot image. actual | Path to the actual image, if one was created. diff | Path to the diff image, if one was created.

Caveats

To make shouldLookSameAs behave like a normal assertion, I've had to use undocumented Cypress features. Be aware that this plugin could stop working after any update to Cypress.