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

v1.0.1

Published

Write BDD-style tests with eloquence.

Downloads

26

Readme

Build Status: TravisCI Latest package version

“What's this?”

This is a drop-in enhancement for Mocha's BDD interface, which adds two small but tangible improvements:

A when() global

This is the same calling describe(), but the description you give is automatically prefixed by "When ":

when("this test is run", () => {
	it('gets prepended with the word "When"', …);
});

Which is a shorter, clearer way of writing:

describe("when this test is run", () => …);

Tests specified by it() actually start with "It "

Mocha makes idiomatic tests fun to write ...

describe("when the app starts", () => {
	it("activates successfully", () => …);
	it("connects to the server", () => …);
	it("receives a valid payload", () => …);
});

... but not as fun to read:

when the app starts
  ✓ activates successfully
  ✓ connects to the server
  ✓ receives a valid payload
  ✓ displays the result

This module fixes such broken language by automatically prefixing each test:

when the app starts
  ✓ it activates successfully
  ✓ it connects to the server
  ✓ it receives a valid payload
  ✓ it displays the result

If a test (or suite) description already includes the expected prefix, it won't be modified. So you needn't worry about stuff like this:

when When the prefix is included
  ✓ it it won't repeat the word "it"
  ✓ it it'll check for contractions too

Usage

  1. Add mocha-when to your project's dependencies:

    # Using NPM:
    npm install --save-dev mocha-when
    
    # Or with Yarn:
    yarn add mocha-when
  2. Activate it by calling the function it exports:

    require("mocha-when")();

    Or simply pass mocha-when/register to Mocha's require option:

    // In your `.mocharc.js` file:
    module.exports = {
    	require: [
    		"mocha-when/register",
    	]
    };

Caveats

  • ESLint won't recognise the when() global, so add it to your globals list.
  • Mocha's ui option is assumed to be bdd (the default).
  • Tests can be declared without an it prefix using specify().
  • The enhancements applied by this module are persistent and irrevocable.