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

with-eyes

v3.0.1

Published

Simple `jest`, `mocha` and `jasmine` high order function to compare screenshots, using [Applitools Eyes](https://applitools.com/). It integrates nicely with [Puppeteer](https://github.com/GoogleChrome/puppeteer) and [Protractor](https://github.com/angular

Downloads

39

Readme

with-eyes

Simple jest, mocha and jasmine high order function to compare screenshots, using Applitools Eyes. It integrates nicely with Puppeteer and Protractor.

Install

npm install with-eyes --save-dev

Example

Here is an example by mocha as test runner:

  const {eyes} = require('with-eyes/mocha');

  describe('my application', () => {

    eyes.it('should open a contacts page', async () => {
      // ... navigate, do actions
      await eyes.checkImage(await page.screenshot(), 'start page'); // using puppeteer
      await eyes.checkImage(await browser.takeScreenshot(), 'start page'); // using protractor
    }));

  });

API

Import eyes from a specific test runner package.

const {eyes} = require('with-eyes/mocha');
const {eyes} = require('with-eyes/jest');
const {eyes} = require('with-eyes/jasmine');

// This import will try to autodect which test runner you are using
// and will reexport from a corresponding package mentioned above.
const {eyes} = require('with-eyes');

And just use it:

// jasmine
eyes.it('...', () => {});
eyes.fit('...', () => {});
eyes.xit('...', () => {});

// jest
eyes.test('...', () => {});
eyes.test.only('...', () => {});
eyes.test.skip('...', () => {});

// mocha
eyes.it('...', () => {});
eyes.it.only('...', () => {});
eyes.it.skip('...', () => {});

It's that easy. It's Wix!

Viewport and environment

Eyes determine a viewport based per first checked image. However due to webpage nature, the webpage (screenshotted image) might change it's size. In order to overcome this, this library automatically sets 100x100 viewport size, so that environment doesn't change due to change in a webpage.

If you want to disable this behavior:

const {useFixedViewPort} = require('with-eyes');

before(() => {
  beforeEach(() => useFixedViewPort(false));
});

Using Baseline name

By default eyes always saves baseline within its environment (combination of OS, Viewport Size and Browser). If you want to compare different browsers you should set Baseline Name.

It is also convenient when you use fullscreen screenshots. It will compare different viewport size images by baseline name.

If you want to use baseline name you should say it explicitly:

const { eyes, useBaselineName } = require('with-eyes');

...

beforeEach(() => useBaselineName(true));

with-eyes will then automagically create baseline name for your tests.

TIP: Don't itroduce useBaselineName with other breaking changes. When introducing baseline name to existing tests find your stable version, add useBaselineName option and run your tests. When tests with baseline name is ran for the first time they appear as new and are not compared to anything.