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-filter

v1.3.0

Published

Util for adding custom filters to Mocha

Downloads

15

Readme

Mocha Filter

This package allows you to add custom filters to the various test stages in the Mocha test framework.

By default (when you require('mocha-filter')) an ignore filter is added, which will completely remove a test (or set of tests) from the test run without leaving a trace in the test output.

Examples

The filters can be used to restrict test runs to only be used when in specific environments:

var filter = require('mocha-filter');

filter.addFilter('preprod', () => {
	return _config.test_env === 'pre-production';
});

describe.preprod('A test set which should only run in pre-production', () => {
	//...
});

So long as the supplied function for the filter returns true, false, or 'skip', you can make it execute whatever you would like, without having to wrap tests in conditionals

filter.addFilter('dataSupplied', () => {
	if (!_config.sample_data) {
		console.error('Error: data not supplied. Skipping test.');
		return false;
	}
	return true;
});

describe('Example tests', () => {
	it.dataSupplied('Test to only run when sample data is supplied', done => {
		//...
		done();
	});
})

You can also add multiple filters at once by passing an object containing all the required funtions, with the key being the name of the filter:

var filter = require('mocha-filter');

var filters = {
	example: () => {
		return true;
	},
	otherExample: () => {
		return false;
	}
}

filter.addFilters(filters);

describe('Using multiple filters', () => {
	it.example('Example test', done => {
		//...
		done();
	})

	it.otherExample('Other Example test', done => {
		//...
		done();
	});
})

Alternatively, you can pass in a default set of filters when requiring the package:

var filters = {
	example: () => {
		return true;
	},
	otherExample: () => {
		return false;
	}
}

var filter = require('mocha-filter')(filters);

describe('Using multiple filters', () => {
	it.example('Example test', done => {
		//...
		done();
	})

	it.otherExample('Other Example test', done => {
		//...
		done();
	});
})