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

cantest

v0.0.2

Published

Canvas visual testing

Downloads

4

Readme

cantest - silly testing for canvas static output

Build Status

cantest is a simple way to validate that a canvas drawing function did not break. It basically executes the test and compares the PNG result to an expected PNG file.

Note that for now cantest can be used (for now) only for static outputs, but it's cool anyway :-).

Use npm to install cantest:

$ npm install -g cantest

You will also need node-canvas for drawing stuff in your tests:

# local install (no -g) - test code requires it
$ npm install canvas

Create a test (e.g. mytest.js):

var Canvas = require('canvas'); 

module.exports = function() {
  var canvas = new Canvas(200, 200);
  var ctx = canvas.getContext('2d');

  // https://github.com/learnboost/node-canvas#example

  ctx.fillStyle = 'orange';
  ctx.fillRect(0, 0, 200, 200);

  ctx.fillStyle = 'black';

  ctx.font = '30px Impact';
  ctx.rotate(.1);
  ctx.fillText("Awesome!", 50, 100);

  var te = ctx.measureText('Awesome!');
  ctx.strokeStyle = 'rgba(128,100,0,0.5)';
  ctx.beginPath();
  ctx.lineTo(50, 102);
  ctx.lineTo(50 + te.width, 102);
  ctx.stroke();

  // the test must return the canvas
  return canvas;
};

Run cantest for the first time. Since mytest.png does not exist, it will be generated by cantest but the test will fail (exit code 1).

$ cantest mytest.js
[mytest.js] mytest.png created

Next time you run the test, it should succeed quitely:

$ cantest mytest.js
$ 

Now, change something in mytest.js. For example, replace:

ctx.fillStyle = 'orange';

With:

ctx.fillStyle = 'green';

And when you run cantest again:

$ cantest mytest.js
[mytest.js] Test failed. See actual output in .actual.mytest.png

The browser window should also open and you should see:

failure

Command line

$ cantest -h
Usage: cantest <files...> {options}

Options:
  -b, --browse   Open browser if test fails to compare results (use --no-browse to negate)  [default: true]
  -v, --verbose  Verbose output                                                             [default: false]
  -h, --help     Show help                                                                

API

cantest(module, [options], [callback))

Executes the function exported by the module. The function should return a Canvas object (created by node-canvas).

  • module is the path to a node.js module.
  • options is optional.
  • options.expected may contain the name of a .png image that contains the expected result. By default, it is assumed to be the name of the test file with a .png extension. For example, if module is test55.js the expected file is test55.png.
  • options.actual can be used to export the actual result into a .png file. Otherwise, it will be written into a temp file which will be deleted (upon success).
  • callback is optional and may contain a function(err, result) where result is:
    • passed - Boolean indicating whether the test passed or not.
    • expected - String path to the png file that contains the expected result.
    • actual - String path to the png file that contains the actual result.
    • test - String the base name of the test file.
    • compare - Optional String with path to an an HTML for comparison between actual and expected.

assert.canvasEqual(c1, c2, [message])

An extension to the assert module which compares two Cavnas objects. Any of c1 and c2 may also be a Buffer.

License

(The MIT License)

Copyright (c) 2011 Elad Ben-Israel

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.