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

taptap

v0.0.3

Published

simple testing function

Downloads

5

Readme

taptap

taptap is simple testing function. you give a test function with "done" param. like that:

var test = require('taptap');
var assert = require('assert');

test(function (done) {
  assert(1);
  done();
});

you should always call "done". taptap will timeout in 2s, you can't alter it.

taptap produces results in tap format (i suppose..).

there may be two reasons when test failed:

  • there were uncaught exceptions in your test functions. like those produced by assertions, for example
  • your test function did not call "done"

in these cases taptap will output stacktrace for the first case and "hanger" test function source code in the second case.

taptap writes to stdout but you could give it another stream to write to if you want. call .pipe on it, like this

var test = require('taptap');
var stream = require('stream').Transform;

test.pipe(new stream).pipe(new stream);

[your tests...]

you could also .skip and .todo tests. like this:

var test = require('taptap');

test.skip(function () {
});

test.todo(function () {
  throw new Error;
});

skip tests are always "ok", todo tests may be either "not ok" (if they don't pass) or "ok" if they pass (gives bonus!).

please check that your test functions are indeed functions!