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

test-decorators

v0.3.1

Published

A set of decorators to run js unit tests with.

Downloads

153

Readme

Test Decorators

npm Build Status Coverage Status

Test decorators provides a set of decorators to run javascript unit tests with.

Please also refer to the Documentation.

Table of contents

Suites

Instead of writing describe, define a class and decorate it with @suite:

import { suite } from "test-decorators";

@suite
class TestSuite {
}

The decorator takes optional options as arguments, to provide a name or have describe.only called instead:

import { suite } from "test-decorators";

@suite("The name provided to describe")
class TestSuite {
}
@suite({
    name: "The name provided to describe",
    only: true
})
class TestSuite {
}

If no name is provided, the name of the class is used.

Tests

Instead of writing it, define a class decorated with @suite and provide methods decorated with @test:

import { suite, test } from "test-decorators";

@suite
class TestSuite {
    @test
    private testSomething() {
        ...
    }
}

The decorator takes optional options as arguments, to provide a name or have test.only called instead:

@test("test something")
private testSomething() {
    ...
}
@test({
    name: "test something",
    only: true
})
private testSomething() {
    ...
}

If no name is provided, the name of the method is used.

Parameterizing

It is possible to parameterize the tests to have them called with different inputs:

@test({
    name: "test something",
    only: true,
    params: [-1, 0, 1, 10, 1000, 2000]
})
private testSomething(input) {
    ...
}

The test will be executed once with every parameter specified.

The name can be generated from the parameters to increase readability:

@test({
    name: ({ a, b, expected }) => `${a} + ${b} is ${expected}`,
    only: true,
    params: [
        { a: -1, b: 1, expected: 0 },
        { a: 0, b: 0, expected: 0 },
        { a: 100, b: 1, expected: 101 }
    ]
})
private testSomething({ a, b, expected }) {
    expect(a + b).tobe(expected);
}

Configuration

This library should work out of the box with jest and mocha compatible framework without any additional configuration needed. Otherwise it is possible to configure it and provide mocha-compatible functions:

import { configure } from "test-decorators"

configure({
    it: () => { ... },
    itOnly: () => { ... },
    describe: () => { ... },
    describeOnly: () => { ... },
});

Contributing

Yarn is used instead of npm, so make sure it is installed, probably: npm install -g yarn.

Install all dependencies using

yarn install

Building

In order to build the code:

yarn build

Running the tests with coverage

yarn test

Linting

yarn lint

Starting the example

cd example
yarn test

Contributors

  • Frederick Gnodtke
  • Sergej Kasper