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

itworksjs

v1.2.0

Published

A simple unit testing library

Downloads

42

Readme

itworks

A simple node unit testing library. It is completly error driven and doesn't need any additional dependencies.

Installation

npm install --save-dev itworksjs

Usage

Create a test file, and set it as npm test in the package.json file. In the test file, follow this example:

const {it, works} = require("itworksjs")

it("should be able to evaluate expressions", ()=>{
    if(1+1*2 != 3){
        throw new Error(`Evaluated 1+1*2 as ${1+1*2} instead of 3`)
    }
})

it("should think 1+1=3",()=>{
    if(1+1 != 3){
        throw new Error(`Evaluated 1+1 as ${1+1} instead of 3`)
    }
})

works()

Then, when testing

[O]: It should be able to evaluate expressions
[X]: It should think 1+1=3 FAILED: Evaluated 1+1 as 2 instead of 3
Tests Finished, Result: 1/2 Passed    

Example using functions

// tested.js
function a(y,z){
    return z+y
}

function b(y,z){
    return y-z
}

module.exports = {a:a}

// test.js
const {it, works, functions} = require("itworksjs")

const {a,b} = functions(["a", "b"]).from("./tested.js")

it("should be able to add", ()=>{
    if(a(1,1) != 2){
        throw new Error(`a(1,1) = ${a(1,1)}`)
    }
})

it("should be able to substract", ()=>{
    if(b(3,4) != -1){
        throw new Error(`b(3,4) = ${b(3,4)}`)
    }
})

works()

Which gives the result:

[O]: It should be able to add
[O]: It should be able to substract

Tests Finished, Result: 2/2 Passed

It Works!

Functions

  • it(message, code): Takes a message (text displayed when testing and identifier) and a function, and adds it to a global tests object (which is created if it doesn't already exist).

  • works(): Tests all functions in the tests object, considers them failed if they throw an error (which is displayed). The function also returns [passedTests, totalTests].

  • functions(functionlist).from(file): Similar to the require function. Imports the functions (given as an array of strings) even if they are not in module.exports.

  • arrayEquals(array1, array2): Checks recursively if two arrays are equal.


Note

console functions were replaced with empty ones, to suppress console logs. Use the new console.print function instead.