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

v1.0.11

Published

suite-level wrapper for mocha's describe

Downloads

6,073

Readme

mocha-suite

Greenkeeper badge

Define suite-level utilities and test structure for mocha tests

Save yourself the hassle of manually constucting suite definitions. Bundle common logic (such as setting up sandboxes) and minimize the number of require() statements in your test files.

Example

  // _suite.js

  const suite = require('mocha-suite');
  const sinon = require('sinon');
  const chai = require('chai');

  module.exports = suite((tests, options) => {
    const sandbox = sinon.sandbox.create();

    afterEach(() => sandbox.restore());

    tests({
      spy: sandbox.spy,
      stub: sandbox.stub,
      expect: chai.expect
    });
  });
  // app.spec.js

  const suite = require('./_suite');
  const MyApp = require('../src/app');

  suite('MyApp', ({ expect, spy }) => {

    describe('someFunc()', () => {
      it('should call spy', () => {
        const bootstrap = spy();

        const app = new MyApp(bootstrap);

        expect(bootstrap.called).to.be.true;
      });
    });
  });

Usage

suite(suiteDefinition, [describe])

Returns a renderedSuite function.

  • suiteDefinition: A function which accepts a test function which must be called in the suite definition in order to run your tests.
  • describe: An override for describe(). Optional

renderedSuite(description, [options], tests)

  • description: Text to distinguish this suite from others, will be passed as the first parameter to describe().
  • options: Any type of object or value representing options which will be passed as the second parameter to the provided suite definition. Optional
  • tests: A function that runs all of your suite's describe()s and it()s when called.

The returned renderedSuite has the properties only and skip which allows it to operate like mocha's describe():

  // isolated.spec.js

  const suite = require('./_suite');

  suite.only('Isolated', ({ expect, spy }) => {
    /* tests will be run exclusively */
  });
  // skipped.spec.js

  const suite = require('./_suite');

  suite.skip('Skipped', ({ expect, spy }) => {
    /* tests will be skipped */
  });