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-test-context

v1.0.0

Published

Captures the current running mocha test name and file path. Useful for certain types of logging/reporting about mocha tests.

Downloads

8,452

Readme

mocha-test-context

Provides a way to get information about the currently running Mocha test, without needing to pass it from the test itself.

Why would I want this?

Yeah, it's kinda niche. You can get this information on a per-test basis from inside a mocha test with this.test. Why not just do that? Probably you're writing some sort of test reporting/logging tool. You need to know the currently running test's name and you don't want to change hundreds of test cases to pass the name of the test down with this.test.title from each and every test.

Or, you have some other process that runs alongside your tests (like puppeteer) and you need a way know what test was running when it dies or something.

Installation

You probably want this as a dev dependency, because it's testware.

yarn add --dev mocha-test-context
# or
npm install -D mocha-test-context

You then need to require mocha-test-context before running the mocha test. This can be done with the argument mocha -r mocha-test-context

Usage

const mochaTestContext = require('mocha-test-context');

describe('my suite', () => {
  it('is my test', () => {
    // ... some mocha test code here...
    console.log(mochaTestContext());
    // this would print:
    //{ title: 'is my test', fullTitle: 'my suite is my test', file: 'test.js' }
  });
})

How does it work?

It reaches into the guts of Mocha's Runnable class and overrides the prototype to capture the data and make it avaliable.