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

@acce/tester

v1.1.3

Published

simple test runner with support for async stuff

Downloads

30

Readme

@acce/tester

This is a crazy simple test framework for node applications.

Usage

To use, import the 'file' method into your test.

import { file } from '@acce/tester';
// or
const { file } = require('@acce/tester');

API

  • file: <function> properties (name, method)

    • name: <string> the name of the unit you are testing.
    • method: <Function> a scope for your file. The method property should be an function that takes one argument, unit
  • unit: <function> properties (name, method)

    • name: <string> the name of the unit you are testing.
    • method: <Function> a scope for your unit. The method property should be an function that takes one argument, test
  • test: <function> properties (name, method)

    • name: <string> the name of the test you are running
    • method: <Function> a scope for your test. The method does not require any arguments.

If you need a simple assertion library, I recommend using node.js assert package

Example test

  1. Create a file called <unit>.test.js somewhere in your project. Where <unit> is the name of the unit you are testing

  2. Add an npm script command to your package.json that will execute your new test. ESModules require the 'experimental modules' flag, and a package.json type property

    {
    	...
    	"type": "module",
    	...
    	"scripts": {
    		...
    		"test:unit": "node --experimental-modules path/to/unit.test.js",
    		...
    	},
    	...
    }
  3. You can now execute your test with npm run test.

    Example Unit Test

    import { file } from '@acce/tester';
    
    file('Maths functionality', async (unit) => {
    	unit('Test that math still works', async (test) => {
    		test('1 + 1 does not equal 3', async () => {
    			if (1 + 1 == 3) throw 'looks like maths is falling appart';
    		});
    
    		test('1 + 1 does not equal 11', async () => {
    			if (1 + 1 == '11') throw 'looks like maths is working with strings now';
    		});
    
    		test('1 + 1 is actually 2', async () => {
    			if (1 + 1 !== 2) throw 'well dang. Computer machine dun\' broke';
    		})
    	})
    })

    Example Output

    exampe of a successful unit test