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

testjs

v1.0.4

Published

A compact testing module for node.js.

Downloads

445

Readme

test.js

test.js is a compact testing module for node.js that simply wraps node's assert module and generates pretty printed output.

  • Small footprint, minimal dependencies
  • Non-utf8 and Windows terminal approved
  • Allows asynchronous testing
  • Allows modular tests by just assembling data structures
  • Simple API and Cli (just testjs)
  • Emphasis on timers
  • Available through npm: npm -g install testjs

Usage

Cli

Place your test suite in tests/suite.js.

// package.json
...
{
    "devDependencies": {
        "testjs": "latest"
    },
    "scripts": {
        "test": "testjs"
    }
}
...

npm test

API

// tests/run.js
var Suite = require("testjs");

Suite.run({
    "firsttest": function(test) {
        ...
        test.done();
    },
    ...
});
// package.json
...
{
    "scripts": {
        "test": "node tests/run.js"
    }
}

npm test

Assertions

All of node's assert (just replace assert through test) plus test.notOk(...) as a negated ok.

  • test#ok(actual) / test#notOk(actual) / test#ifError(actual)
  • test#equal(actual, expected) / test#notEqual(actual, notExpected)
  • test#deepEqual(actual, expected) / test#notDeepEqual(actual, notExpected)
  • test#strictEqual(actual, expected) / test#notStrictEqual(actual, notExpected)
  • test#throws(blockFunction[, classRegExpOrValidationFunction]) / test#doesNotThrow(blockFunction)

There is also a test#log(...) for logging straight to the test console.

Self-explaining examples

When typing testjs in a terminal, tests/suite.js will be run. Also supports running runners: testjs tests/run.js or custom / other unit tests under the condition that the runner (here: run.js) does not export anything. If it does, whatever it exports will be run.

Interoperability

test.js is partially interoperable with nodeunit. There is no setUp/tearDown however and there are no aliases for things like equal, which is for example aliased as equals in nodeunit. However, test.js including dependencies is about 100kb while nodeunit is about 16mb.

Command line options

| Option | Function | -------------------------- | ----------------------------------------------------------------------------------------- | --nocolors or -nc | Disables terminal colors. | --name=NAME or -n=NAME | Sets the suite name. Defaults to the name defined in package.json which is looked up inside of the current working directory or to the base name of the suite file if there is no package.json. The hard coded default is suite. | --silent or -s | Does not produce any output.

Always returns the number of failed tests as the status code.

Example: testjs --name=MyGame -nc tests/mygame-test.js

License

Apache License, Version 2.0