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

@gowerstreet/infintestimal

v1.1.1

Published

A minimal predicate-based testing library for Sibilant

Downloads

2

Readme

Infintestimal

A minimal predicate-based testing library for Sibilant

Rationale

Most JavaScript testing libraries are written around the idea that when a test fails, it throws. As to why this might be considered a bad idea, have a look at Joel Spolsky's blog post 'on exceptions'.

If you agree with this viewpoint, you might think it would be nice to have a testing library where a test is basically just a function that returns true or false, and a test suite is just a list of tests, and a test runner is a function that just maps over this list transforming test functions into output.

This is what Infintestimal does. It is written in Sibilant, a LISP that is a very shallow transformation to readable JavaScript, but the code is useable from plain old JS, like so example-test.js:

var {is, testRunner} = require('@gowerstreet/infintestimal')

var exampleSuite = [["This is a test that passes",
                     () => is(1, 1) ],
                    ["This is a test that fails",
                     () => is(1, 2) ],
                    ["We can compare arrays",
                     () => {let result = [1, 2]
                            return is([1, 2], result)} ],
                    ["We can also compare objects",
                     function named (){let result = { a: 1, b: 2 }
                                       return is({ b: 2, a: 1 }, result)} ],
                    ["Comparisons that fail show the expected and actual",
                     () => is({ a: 1, b: 2 }, { a: 1, b: 1 }) ],
                    ["We can test async functions",
                     (done) => setTimeout(() => done(is(1,1)), 1000) ]]

testRunner(exampleSuite)

The first line imports the is and testRunner functions from the infintestimal library.

The next line creates a test suite, an array of test tuples. Each test tuple has a name and a thunk (a function with no parameters) that returns the result of calling is which is the equivalent of assert.equal(expected, actual) for values and assert.deepEqual(expected, actual) for arrays and objects.

Finally the call to testRunner with the suite of tests (which are just data) runs the tests and prints the results.

As you can see from the last example, testing an async function just requires that you pass a callback function to your test function, and then call it with the results of evaluating is on your expected and actuals.

Running this with node example-test.js produces the following output:

Running tests...

This is a test that passes ✔
This is a test that fails ✘
  expected 1 but got 2
We can compare arrays ✔
We can also compare objects ✔
Comparisons that fail show the expected and actual ✘
  expected {
  "a": 1,
  "b": 2
}
but got {
  "a": 1,
  "b": 1
}
✔ We can test async functions
4 tests passed, 2 failed