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

mocha-runner-hooker

v1.0.3

Published

Additional functionality for each mocha test by hooks

Downloads

5

Readme

mocha-runner-hooker

Released

Simple hooker for mocha

Installation

npm i mocha-runner-hooker

The main idea we could add to describe, as much some types hooks as we want and they are going to be executed in orded as were added

  • No necessary add repeated hooks in each test just do it once in mocha-runner-hooker.
  • Or add new functionality for all your 1000 test cases through mocha-runner-hooker
  • Works with top level and nested describes (isTopLevelSuiteIncluded option)
  • Supported globalSetup functions array (the same like hooks)
  • Supported globalTeardown functions array (the same like hooks)
  • Supported custom reporter and substring title filter for describes

Add new hooks to runner

//testRunner.js
import {RunnerHelper} from 'mocha-runner-hooker';

RunnerHelper.runner([
    {
        hookType: 'before all',
        hookTitle: 'hello',
        order: 'Top',
        hookFn: () => {
            console.log('Hello from before');
        },
    },
    {
        hookType: 'after all',
        hookTitle: 'hello',
        order: 'Top',
        hookFn: () => {
            console.log('Hello from after');
        },
    },
    {
        hookType: 'after each',
        hookTitle: 'hello',
        order: 'Top',
        hookFn: () => {
            console.log('Hello from after each');
        },
    },
    {
        hookType: 'before each',
        hookTitle: 'hello',
        order: 'Top',
        hookFn: () => {
            console.log('Hello from before each');
        },
    },
]);

and just add path to file with runner in your package.json scripts

 "testRunner": "mocha ./testRunner.js ./tests/test.js --no-exit || exit 0",

skip runner already was prepared (skip all it in describe if one was failed)

 "testSkipRunner": "mocha ./node_modules/mocha-runner-hooker/skipRunner.js ./test/test.js --no-exit || exit 0",

API

interface Runner {
    hooks: Array<HookType> | null;
    globalSetup?: Array<{argsThis: any; fn: () => any}> | null;
    globalTeardown?: Array<{argsThis: any; fn: () => any}> | null;
    options?: {
        reporter?: any;
        titleIdFilter?: Array<string>;
        isTopLevelSuiteIncluded?: boolean;
    };
}

type HookType = {
    hookType: 'before all' | 'before each' | 'after each' | 'after all';
    hookTitle: string;
    order: 'Top' | 'Bottom';
    hookFn: () => any;
};