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

v1.0.0

Published

A better way to mock in Mocha

Downloads

1

Readme

mocha-using

A smarter way to mock in Mocha.

Description

If you ever find yourself writing large mocked functions that have giant switch/conditional statements used to determine what test is currently happening and how the current mock should respond, this module is for you!

In the background, this module uses proxyquire to handle the mocks. This means the only code values you can mock are require() responses. For me, this really made sense because code should be unmodified when testing and doing coverage reports.

Installing

npm install --save-dev mocha-using

Using

my-module.js

var crypto = require('crypto');

module.exports = function(cb){
    crypto.randomBytes(16, cb);
};

test.js

const chai = require('chai');
const expect = chai.expect;

// our stubs (could be in separate file)
const stubs = use => {
    return {
        crypto: {
            randomBytes: function(bytes, cb){
                // we are simply going to look at the `using` object and grab the args the mock
                // should return from that object's `randomBytesResponse` value
                var response_args = 
                    use.randomBytesResponse || 
                    [null, Buffer.from('ffffffffffffffffffffffffffffffff', 'hex')];
                process.nextTick(() => {
                    cb.apply(null, response_args);
                });
            }
        }
    }
};

// note: need to pass the `it` function
const using = require('mocha-using')(it);

// works like a normal require but will use proxyquire to add the stubs
const myModule = using.require('./my-module.js', stubs);

// ready to write our unit tests!
describe('MyModule', () => {
    using({
        randomBytesResponse:[null, Buffer.from('000102030405060708090a0b0c0d0e0f', 'hex')]
    })
    .it('should return 16 random bytes', done => {
        myModule((err, bytes) => {
            if(err) throw err;
            // this would normally be random but, with our stub, we get a consistent value
            expect(bytes.toString('hex')).to.equal('000102030405060708090a0b0c0d0e0f');
            done();
        });
    });
    
    using({
        randomBytesResponse:[new Error('bad juju!')]
    })
    .it('should pass errors back', done => {
        myModule((err, bytes) => {
            expect(err).to.be.instanceOf(Error);
            expect(err.message).to.equal('bad juju!');
            done();
        });
    });
    
    it('should return 16 random bytes', done => {
        myModule((err, bytes) => {
            if(err) throw err;
            // although we didn't pass any data to use for this test, the stub is
            // still active and will use the default
            expect(bytes.toString('hex')).to.equal('ffffffffffffffffffffffffffffffff');
            done();
        });
    });
});

Note: You can also do using().it.only() and using().it.skip() as well!

That mostly sums up the supported functionality. Let me know if you like it or have feature requests/bugs! Thanks for checking out my module!