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 🙏

© 2026 – Pkg Stats / Ryan Hefner

andrew-testing

v1.0.1

Published

Andrew Testing Library is a CLI JavaScript tool for testing JavaScript/Typescript code

Readme

SETTING ANDREW TESTING LIBRARY UP

Download the latest version Andrew Testing Library here, extract it somewhere inside the folder of your project and then create a folder named test and a file named example.spec.ts, then proceed to the next section.

WRITING YOUR FIRST TEST

Paste the following code into the example.spec.ts file then save it.

import { AndrewTesting } from "../core/assert";

AndrewTesting.describe("This is your first test!", () => {
  AndrewTesting.test("Checks if the sum of two numbers is equal to 8", () => {
    const num1 = 4
    const num2 = 4;
    const sum = 8;

    AndrewTesting.shouldBeEqual(sum, 8);
  });
});

The test above checks whether the sum of two numbers is equal to 8. Now open your terminal at the folder where you saved your test and type node example.spec.js (note that you should compile your TypeScript file to JavaScript first). You should get the following output in the terminal:

describe(title, () => {}) creates a test suit, a group of tests, whereas test(title, () => {}) refers to each one of the tests.

MATCHERS

  • shouldBeEqual
  • shouldNotBeEqual
  • shouldBeStrictEqual
  • shouldNotBeStrictEqual
  • shouldBeNull
  • shouldNotBeNull
  • shouldBeUndefined
  • shouldNotBeUndefined
  • shouldBeTruthy
  • shouldBeFalsy

MATCHERS FOR NUMBERS

  • shouldBeGreaterThan
  • shouldNotBeGreaterThan
  • shouldBeGreaterThanOrEqual
  • shouldNotBeGreaterThanOrEqual
  • shouldBeLessThan
  • shouldNotBeLessThan
  • shouldNotBeLessThanOrEqual

MATCHERS FOR COMPARING ARRAYS AND OBJECTS

  • shouldBeEqualArr (for arrays)
  • shouldNotBeEqualArr (for arrays)
  • shouldBeEqualObj (for objects)
  • shouldNotBeEqualObj (for objects)