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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mangar2/testrun

v2.1.0

Published

Runs testcases from test descriptions in JSON files

Readme

Abstract

This module provides a simple test framework to run unit test. You have to provide a list of json files with test cases and several callback functions

Test case schema

The test case definition in each file must follow the following schema:

{
    type: 'array',
    items: {
        type: 'object',
        properties: {
            description: { type: 'string' },
            tests: {
                type: 'array',
                items: {
                    type: 'object',
                    properties: {
                        description: { type: 'string' }
                    },
                    required: ['description']
                }
            }
        },
        required: ['description']
    }
}

Callbacks

Define the following callbacks to run the tests

Prepare

Prepare is called for each testcase. Use it to prepare the object to test and return it

.on('prepare', testcase => {
    // testcase is the full object structure of one testcase, one element of the topmost array
    return myTestObject
})

Run

Run is called for each test. Use it to run the test and return the result

.on('run', (test, object) => {
    // test is the full object structure of one test, one element of the inner array (property tests)
    return object.callFunctionToTest(test.data)
})

Validate

Validate is called for each test. Use it to validate the result

.on('validate', (result, test, path) => {
    // path contains all information about the current test: filename/testcase description/test description
    .unitTest.assertEqual(result, test.result, path)
})

break

Break is called, if you reques to run the test again (for esample on validation error). Then it will be called before the same test runs again. Use it to add a breakpoint and start debugging

.on('break', (test, object) => {
    // redo the test for debugging
    return object.callFunctionToTest(test.data)
})

Methods

new TestRun(verbose) creates a new testrun object. Use verbose, if the framework shall log each step.

run

Use run(fileNames) to run the testcases

on

Use on to register the callback functions (prepare, run, test, validate, break)

runAgain

Use it to run the last testcase again. It is usually called in "Validate" on validation error to simplify debugging.

unitTest

Use the getter unitTest to get the unit test object (see module @mangar2/unittest)