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

testkitten

v0.0.2

Published

Very basic test framework

Downloads

1

Readme

TestKitten

Very basic test framework. The idea is to have 3 funcitonalites:

  • each test is a simple named function
  • function gets a callback as argument which is a trigger to mark it as failed, and to aggregate assert functions
  • tests can be easily packed into separate files and imported into main one

Also a core function is NOT to have any autodiscovery. Each test must be explicitly marked to be executed.

Sample

Please have a look at node_modules/testkitten where there are alltests.spec.js files, which is a test bundle, and it includes test files like failure.spec.js Every test file can be written as a separate test, or bundled into main one for more rapid development.

let specs = ["failure.spec",    // table with tests, string is shown as an INFO for developer to know from which file tests are used
    iMustFail, checkAssertEqualsPasses, checkAssertEqualsArraysPasses, checkAssertJsonEqualsPasses 
]; 
module.exports = specs;

// if it is standalone execute, then initialize tests; otherwise module returns 'specs' array and root tests executes it
if (require.main == module) {
    let testkitten = require('testkitten');
    
    testkitten(specs);    

}

function iMustFail(fail) {
    fail("Yes"); // fail is a funciton, if it has string passed, then it is a failed message; it can also accept object with assert instructions
}


// some samples of assertions
function checkAssertEqualsPasses(check) {
    check({'assertEquals':['a','a']});
}

function checkAssertEqualsArraysPasses(check) {
    check({'assertEqualsArray': [ [1,2,3,4], [1,2,3,4] ] });
}

function checkAssertJsonEqualsPasses(check) {
    check({'assertJsonEquals': [ 
        {'a':'OK', 'source':[1,2,{'x':'other'}]}, // here order is a, source
        {'source':[1,2,{'x':'other'}], 'a':'OK'}] // here order is source, a
    });
}

license

ISC