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

automated-screenshot-diff

v0.1.5

Published

Automated Screenshot Diff - Continuous Safe Deployment Made Easy

Downloads

7

Readme

automated-screenshot-diff NPM version

Continuous Safe Deployment Made Easy

Why?

Although testing gains evidence in software development every day, it is still rare to find a test strategy that goes beyond functional testing. While layout testing remains forgotten by most, we all have seen cases where the application functionally works just fine but that button somehow got moved 2 pixels do the right or that table cell lost it's alignment and the client won't approved it. Manually testing each screen tends to be error prone since some changes are too small for a QA to notice (specially after seeing dozens of other screens) and it can take weeks depending on the system's size and complexity. Automated Screenshot Diff allows you and your team to extend test coverage up to the application layout, making sure yor're aware of any layout changes whether you use manual or automated testing strategies.

How it Works?

It's simple. All you have to do is generate your system's screenshots with a simple naming convention: Example:

SCENARIO_NAME-VERSION.png // login_screen-v1.png

Then automated-screenshot-diff will scan your screenshot's folder and calculate differences between your pre-production (stage) release and your production release. All generated image diffs will be in the same directory as your screenshots. If you don't known how to gereate those screenshots, take a look at examples folder.

Dependencies

Installation (Mac)

$ xcode-select --install
// download and install XQuartz: http://xquartz.macosforge.org/downloads/SL/XQuartz-2.7.5.dmg
$ brew install cairo
$ export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/opt/X11/lib/pkgconfig
$ npm install -g automated-screenshot-diff

Usage Examples

Screenshot Example

To compare release v1 and v2.

$ automated-screenshot-diff compare --previous-release v1 --current-release v2 --source screenshots/

To compare release v1 and v2, ignoring not changed scenarios.

$ automated-screenshot-diff compare --previous-release v1 --current-release v2 --source screenshots/ --ignore-not-changed=true

To compare release v1 and v2, and saving the analysis as HTML.

$ automated-screenshot-diff compare -p v1 -c v2 -s screenshots/ -o html

To compare release v1 and v2, and saving the analysis as JSON.

$ automated-screenshot-diff compare -p v1 -c v2 -s screenshots/ -o json

Demonstration

login_widget-v1.png

login_widget-v1.png

login_widget-v2.png

login_widget-v1.png

Perceptual Diff Between login_widget-v1.png and login_widget-v2.png

login_widget-v1.png

HTML Ouput example

v1-v3-diff.html