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

forking-tap

v0.1.1

Published

Run every single tap test in its own process.

Downloads

26

Readme

forking-tap Build Status Coverage Status

Run every single tap test in its own process.

forking tap takes a single tap-mocha test file:

require('tap').mochaGlobals()
var foo = 'bar';

describe('foo', function () {
	function fooHelper() {}

	it('foo-1', function () {});

	it('foo-2', function () {});
});

describe('bar', function () {
	function barHelper() {}

	it('bar-1', function () {});
});

And splits it into multiple files with one test each:

require('tap').mochaGlobals();
var foo = 'bar';

describe('foo', function () {
	function fooHelper() {}

	it('foo-1', function () {});
});
require('tap').mochaGlobals();
var foo = 'bar';

describe('foo', function () {
	function fooHelper() {}

	it('foo-2', function () {});
});
require('tap').mochaGlobals();
var foo = 'bar';

describe('bar', function () {
	function barHelper() {}

	it('bar-1', function () {});
});

Notice how all the appropriate helper functions and shared variables make it into each test. tap already forks and runs each file in a new process, so you just need to run the standard tap command and pass in the generated files.

Install

$ npm install --save forking-tap

Usage

const forkingTap = require('forking-tap');

const results = forkingTap(fs.readFileSync('./all-the-tests.js', 'utf8'));

results.forEach((result, testNum) => {
  fs.writeFileSync('./test-number-' + testNum, result.code);
});

*Note: * forking-tap currently only provides a transform. It does not provide a means of reading in file(s) or writing the results to disk. That may change in the future. (Help wanted!)

API

testList = forkingTap(source, [options])

Returns testList an array of testResult objects that represent the input source split into individual test files with one test per file.

source

Type: string

The original source code.

options

options.filename

Type: string

The name of the file being split up. Required for source map support.

options.sourceMaps

Type: boolean
Default: true

Forcefully turn off source map support by setting this to false. Otherwise, source map support is turned on if the filename option is present.

options.attachComment

Type: boolean
Default: false

Automatically attach an inline source map comment to the end of the generated code.

testResult

testResult.code

Type: string

The full source code for an individual test

testResult.map

Type: object

The source map descriptor object for the transform (or undefined if filename was not provided, or options.sourceMaps === false).

testResult.nestedName

Type: Array.<string>

A representation of the test name. The last element of the array will always be the string value passed to it(str, fn) test. The preceding elements of the array represent the names of any enclosing describe blocks.

For example, the following:

describe('foo', function () {
  describe('bar', function () {
    it('baz', function () { /* ... */ });
  });
});

would produce a nestedName of`:

['foo', 'bar', 'baz']

License

MIT © James Talmage