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

unit-tester

v2.0.1

Published

A very simple framework for unit tests

Downloads

16

Readme

unit-tester

A simple framework for simple unit tests

Premise

This is a simple library for very simple and limited unit testing.

I had to write it I was taking a bus for 6 hours and had no internet to add Mocha to a project.

Output example:

☁  unit-tester [master] ⚡  ./test.mjs ./
________________________________________________________________________________________________
	.//demo.test.mjs
🧪 core
	🧪 Array
		✅  -> #lastIndexOf
		✅  -> #findLastIndex

		 ✅|All Tests Passed|✅

Installation

~$ npm i unit-tester --save-dev

Usage Notes

~$ mkdir tests
~$ touch tests/something.test.mjs
~$ edit tests/something.test.mjs
import assert from "node:assert"
import { Tests, Test } from "unit-tester"
export default {
  "core": {
    "Array": {
      "#lastIndexOf": () => {
        const arr = [5, 2, 3, 2, 1];
        assert.equal(lastIndexOf(arr, 2), 3);
        assert.equal(lastIndexOf(arr, 5), 0);
        assert.equal(lastIndexOf(arr, 4), -1);
      },
      "#findLastIndex": () => {
        const arr = [5, 2, 3, 2, 1];
        const euqals = number => element => element === number;
        assert.equal(findLastIndex(arr, euqals(2)), 3);
        assert.equal(findLastIndex(arr, euqals(5)), 0);
        assert.equal(findLastIndex(arr, euqals(4)), -1);
      }
    }
  }
}
~$ node_modules/u-tester/test.mjs test

Pro tip:

Add this command "test": "node_modules/u-tester/test.mjs test" to "scripts" section in your package.json.

Now you can use ~$ npm test to test. Also you can replace the test folder with whatever folder name suits you best.

Managing and writing tests

All tests must be in files with .test. in their name e.g. router.test.mjs

All files should be in a folder provided in the command e.g. node_modules/u-tester/test.mjs test

The Tester will read all such files in the designated folder and run the tests automatically.

The .test. files should export default a test tree.

Test functions can be async if needed.