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

itty-bitty-test

v1.0.3

Published

A teensy weensy test library, including a minimal test runner.

Downloads

3

Readme

itty-bitty-test

A teensy weensy test library for Node.js with a tiny test-runner too.

Design objectives

  1. Very minimal. No run-time dependencies.
  2. No checkers, instead use Node.js's built-in assert module, or use something like should.js or Chai if you must.
  3. Does not corrupt the global namespace. Yes, almost every other testing library, I'm looking at you.

How to install

npm install --save-dev itty-bitty-test

Examples of use

Itty-bitty-test exposes three functions to help you write tests:

  • describe - acts as a wrapper for tests. Doesn't currently nest. Also has a synonym: context.
  • it - is a test. Has a name and a callback with no parameters (a 'thunk'). Registers the test without actually running it.
  • reporter - runs the tests and reports their results

A simple test suite might look like the following (ES5):

var t = require("itty-bitty-test");
var assert = require("assert");

t.describe("A calculator", (function() {
  t.it("should be able to add", (function() {
    assert.equal((1 + 3), 4, "two plus two is four");
  }));
  t.it("should be able to multiply", (function() {
    return assert.equal((2 * 3), 6, "two times three is 6");
  }));
}));

t.reporter(console.log);

Of which the output looks like this:

✔ A calculator - should be able to add
✔ A calculator - should be able to multiply

Hacking on itty-bitty-test

You probably don't want to do this, because it was written in Sibilant.js, more as an experiment than anything else. If you really want to raise a PR, please feel free, but don't be surprised of I don't accept it because e.g.

  • Isn't written in Sibilant
  • You've 'helpfully' translated it to ES3/4/5/6/7/Next/Babel/CoffeeScript/TypeScript/Whatevs
  • Doesn't itself have tests, written using itty-bitty-test (obviously)
  • Isn't written in idiomatic Lisp (any of them)
  • Goes against any of the design principles as stated at the top of this page

As I said above, you probably don't want to do this... but if you decide to anyway, build the JS from ./src to ./lib with:

npm run build

and run the tests against the now built JS with:

npm test

Bon appetite!