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

unit-test

v0.0.9

Published

Utility to run unit tests

Downloads

75

Readme

unit-test

The unit-test module is a very light-weight unit test runner that was created simply to satisfy a need for something that did this job when I was in an internet-free zone. Feel free to fork and make improvements.

Currently you get:

var UnitTest = require('unit-test'), // namespace entity
    TestSuite = UnitTest.Suite, // the test runner
    Assertions = UnitTest.Assertions; // selection of assertions to use in tests

// run specifically named test files
TestSuite.namedFiles('testA.js', 'testB.js');

// find all matching test files and run those
TestSutie.paths(__dirname__, 'tests/**.js');

Each test file loaded by the test suite should export an object that contains optional setUp and tearDown functions and any number of functions that begin with the word test. For example:

var Assertions = require('unit-test').Assertions;

module.exports = {
   'setUp':    function() { /* do something */ },
   'tearDown': function() { /* do something */ },
   
   'testCheck whether something is false': function() {
      Assertions.assertEquals(!1, false);
   },
   'testCheck whether something is false with a name': function() {
      Assertions.assertEquals("Checking something is false", !1, false);
   }
};

For convenience, unit-test also includes sinon as require('unit-test').Sinon, Sinon (www.sinonjs.org) is a fantastic library for mocking, stubbing and spying on functions and objects in any unit test.