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

assert-raisins

v2.0.0

Published

Minimalistic test runner that does NOT dynamically require test files. And so `ars --inspect-brk` will have all project files loaded.

Downloads

9

Readme

Assert-raisins

Minimalistic, debugger friendly test runner for Node.

Inspired by baretest

Features

  • fast
  • parallel
  • run test for a line number
  • no nesting
  • better test cleanup (than after hooks)
  • esm
  • typescript types included

Usage

Install:

npm i --save-dev assert-raisins

Write a test test/firstTest.js:

import { test } from 'assert-raisins'
import assert from 'node:assert'

test('first passing test', () => {
  assert.ok(true)
})

test('first failing test', async () => {
  assert.equal(1, 2)
})

Run all tests:

./node_modules/.bin/ars test/**/*Test.js

Run individual test:

# by line number
./node_modules/.bin/ars test/someTest.js:123

Other things available:

  • it which is an alias for test
  • beforeEach() to run some code before each test in a file
  • beforeAll() to run some code before all tests in a file

Test cleanup

Use cleanup function to register some cleanup hook. If it happens to be called within beforeAll, it will be executed "after all". If it's called within beforeEach, it'll be run "after each", and if it's called within a test, it will be executed after that test. cleanup can be invoked multiple times.

In this example, the server will be stopped after each test:

import { cleanup } from 'assert-raisins'

class Server {
  start() {
    ...
    cleanup(() => this.stop())
  }
}

beforeEach(async () => {
  const server = new Server()
  await server.start()
})

Parallel tests

When running multiple test files, the load is distributed between concurrent workers (limited by the number of CPU cores). Each worker is passed TEST_WORKER_ID environment variable (so you can, for instance, create that many test databases).

typescript, jsx, sourcemaps, code coverage

Use NODE_OPTIONS environment variable for any of that. For example, for typescript:

NODE_OPTIONS="--enable-source-maps --loader ts-node/esm" ./node_modules/.bin/ars test/*.test.ts