snapjerk

web application screenshot testing in docker.

snapjerk is a small script that wires together a few webjerk plugins. it runs element-wise screenshot testing in real browsers in a docker container.

specifically, it:

• generates screenshots of elements
• compares captured shots from a reference set of shots with webjerk-image-set-diff
  • if no reference images are found, the first generated set are designated as references
• creates a visual, interactive report when differences detected

usage

cli

🛰 $ snapjerk --help
 
  web application screenshot testing in docker
 
  Usage
  // cli only execution
  $ snapjerk -s /path/to/static-site-directory -d '[{ selector: "body", name: "body" }]' # json or js array 
 
  // using a snapjerk.config.js
  $ snapjerk
 
  // use a custom config file
  $ snapjerk -c /path/to/snapjerk/config.js
 
  Options
  -s, --static <directory>
  -c, --config <filename>
  -d, --definitions <snap-definitions>

library

API documentation lives here.

var snapjerk = require('snapjerk')
var conf = { ... } // see API docs
snapjerk(conf).then(...) // `snaps/` will be a dir with the result of `webjerk-snaps` within!

approving changes

changes come in three forms:

• new images
  • approve by setting WEBJERK_ALLOW_NEW_IMAGES=1 in your env
• changed images
  • approve changes by setting WEBJERK_APPROVE_CHANGES=1 in your env
• removed images
  • approve by simplying removing the images from your reference set
  • PRs to automate this would be great!

for more on the image diffing and approval processes, see webjerk-image-set-diff.

debug

• set DEBUG=webjerk* to enable verbose logging
• node --inspect-brk node_modules/.bin/snapjerk, just like any other old node process :)

why?

great options out there for testing visual diffs in browsers are slim. i've drawn the conclusion that most people roll their own image snap and comparison solutions, or, bring in large swaths of dependencies and configuration to make it all work.

this project aims to sceenshot testing really easy. by easy, i mean:

• minimal dependencies
• minimal configuration
• small API surface
• easy to debug & hack on
• host agnostic screenshots. different browsers on different boxes yield different visual rendering. browsers in docker resolves that.

the nearest thing to this project is (BackstopJS)[https://github.com/garris/BackstopJS]. it's great! it's more comprehensive than this package, but also brings with it more complexity. give it a shot if snapjerk doesn't work out for you.

arch

just in case you cared to know. happy hacking.

• snapjerk digests user config & instantiates the webjerk-snaps plugin
• snapjerk registers the webjerk-snaps plugin instance with webjerk, and runs webjerk
• webjerk runs the main and post hooks on webjerk-snaps
  • main boots the browser in docker and takes screenshot
  • post generates a diff report (optionally)
• unwind & exit

easy peasy.

faq

• "what browsers are supported?"
  • ATM, just chrome. this package used to support firefox, but in efforts to remove complexity and the overhead of selenium, it has been removed.
    • we now use an adapter based strategy.
  • PRs to make a firefox/slimer/etc adapter would be accepted!
• "how do i navigate, or, do <some-action-in-the-browser> before or after taking screenshots?"
  • see the SnapsConfig.onPreSnap/SnapsConfig.onPostSnap options