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

@opeltre/testo

v0.0.0

Published

Testing utility based on writer & error monads

Downloads

13

Readme

Testo

A small testing utility based on the Writer monad.

npm i @opeltre/testo

Tracer Monad

The Tracer monad logs strings alongside Maybe values.

//  Tracer a = Writer (Maybe a)

//  ta : Tracer Int
let ta = [1, ['all', 'good']]

//  tb : Tracer Int 
let tb = [null, ['oops', 'no int!']]

All tests return values inside the Tracer monad, e.g.

//  unit : () -> Tracer Bool 
let unit = () => {
    let expect = 1, 
        obtain = someIntFunction(); 
    return expect === obtain 
        ? [true, ['1 = 1']],
        : [false, [`1 != ${obtain}`]];
}

Running tests

Each testing file exports a collection of unit tests, which are functions to the Tracer monad.

    File = {Unit} 
    Unit = () -> Tracer a

Units are run one by one by providing test.run the files to be tested, e.g.

//  tests.js
let test = require('@opeltre/testo');

let a = require('./fileA.js'),
    b = require('./fileB.js');

test.run({a, b}); 

Running $ node tests.js will then log all encountered errors if any, and provide some feedback.

Writing unit tests

The main test object exports comparison functions to conveniently write these tests.

//  fileA.js
let test = require('@opeltre/testo');

//     .t1 : () -> Tracer ()
exports.t1 = () => {
    let expect = [0, 1, 2],
        obtain = [0, 1, 3]; 
    return test(expect, obtain);
}

//     .t2 : () -> Tracer ()
exports.t2 = () => 
    let expect = {a: [0, 1]},
        obtain = {a: [0, 1], b: [1, 2]};
    return test(expect, obtain); 
}

Using with npm

Edit your package.json to:

... "test": "node tests.js"

And run $ npm test