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

image-comparison-frontend

v3.4.2

Published

Frontend of an image comparison solution. Performs image comparisons during end to end tests and writes test results

Downloads

21

Readme

image-comparison-frontend

Frontend of an image comparison solution. Performs image comparisons during end to end tests and writes test results

Installation

yarn add image-comparison-frontend
or
npm install --save image-comparison-frontend

Usage

Configuration

You can specify a reportPath (relative to the current directory) to define where to put the .test-result.json files.

ImageComparison will use the protractor-image-comparison screenshotPath by default.
ResultReporter will use test-results in the current directory by default.

With protractor-image-comparison

Configure protractor-image-comparison.
Note: returnAllCompareData must be set to true!

In your test, create an ImageComparison instance const imageComparison = new ImageComparison({config...});
and call a check function, for example await imageComparison.checkPage('startPage');)

use custom image comparison together with ResultReporter

Create a ResultReporter with const reporter = new ResultReporter({config...})
and after running your test, call await this.reporter.report(...); with a Result object containing information about the test run.

See src/image-comparison.ts for inspiration.

API

checkElement

checkElement(
    elementFinder: ElementFinder,
    testName: string,
    protractorImageComparisonOptions?: any
): Promise<void>

creates an image from the specified element and - if the base image already exists) compares it to the base image.

elementFinder: is any valid Protractor element finder, for example element(by.id('myElement'))
testName: a unique name for your test, for example 'anElement after adding'
protractorImageComparisonOptions: optionally, you can add additional configuration that is passed through to protractor-image-comparison

returns a Promise resolving to void

checkPage

checkPage(
    testName: string, 
    protractorImageComparisonOptions?: any
): Promise<void> 

Convenience function to create an image with checkElement specifying the page <body> as element.

testName: a unique name for your test, for example 'anElement after adding'

returns a Promise resolving to void

Notes