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

testnow

v2.0.9

Published

Minimalistic testing framework designed for writing inline tests

Downloads

23

Readme

testnow

Minimalistic testing framework

    npm install testnow

This framework doesn't have any CLI, only programmatic API.
It's designed to be cross-platform and to be able to be integrated with any build / CICD / deployment tools.

Examples are in typescript.

Setting up / describing tests

import test from "testnow";

function mySetImmediate(cb: () => void) {
    return setTimeout(cb, 0);
}

test.group("mySetImmediate", () => {
    test("Executes callback", (end: test.Handler) =>
        mySetImmediate(() => end()));

    test("May be cancelled with clearTimeout", (end: test.Handler) => {
        let timeoutId = mySetImmediate(
            () => end(new Error(`Callback executed`))
        );
        clearTimeout(timeoutId);
        setTimeout(() => end(), 100);
    });
});

Executing tests

nodejs

import test from "testnow";

import "./mySetImmediate";
import util from "util";

test.run().then(result => {
    console.log(util.inspect(result, true, 10, true));
});

Several simple reporters are now built in testnow. Reporter is simply a function that takes test results and does something with them. Usually reporters output the results somewhere. Right now there are 4 simple reporter types: plain - using the most basic and cross-platform console.log functionality, console and terminal - are similar to plain for now, dom - inserts a html-formatted report as innerHTML into a given dom-node. The reporter export provided by testnow contains not reporters themselves, but reporter creators, functions that have optional reporter-options object as a parameter and return a reporter. We could rewrite the above example using a simple built-in reporter which just logs results to the console:

import test, {reporter} from "testnow";

import "./mySetImmediate";

test.run().then(result => {
    reporter.plain({})(result);
});

browser

import test, { reporter } from "testnow";

window.onload = () => {
    test.run().then(result => {
        reporter.dom({})(result);
    });
}

We should compile the code above into a bundle.js somehow, and then we can see the results using following html:

<html>

<head>
    <script src="bundle.js"></script>
</head>

<body>

</body>

</html>