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-nock-fixtures

v0.2.0

Published

A simple library that makes saving fixtures with nock and mocha easy.

Downloads

10

Readme

Mocha Nock Fixtures Build Status

About

A simple library that makes saving fixtures with nock and mocha easy. Just use describeFixture instead of describe and it will record outbound requests using nock into test/fixtures and read from them the next time you run the tests.

Install

npm install --save-dev mocha-nock-fixtures

Usage

Use describeFixture instead of describe and it will use nock to record all requests into your test/fixtures directory. It also supports .skip and .only as mocha does.

var request         = require('request');
var assert          = require('assert');
var describeFixture = require('mocha-nock-fixtures');

describeFixture('normal test', function() {
  it('works', function(done) {
    request('http://localhost:4000/users', function(err, res, body) {
      assert(!err, 'was success');
      done();
    });
  });

  describe('some other test', function() {
    // You can use mocha how you normally would to group tests
  });
});

describeFixture.skip('skipped test', function() {
  // Anything in here will be skipped
});

describeFixture.only('only test', function() {
  // This will be the only test run
});

// Usage with test specific options
//
// This test will not record the request to localhost:4000 and anything it does
// record it will also record the reqheaders
describeFixture('normal test', {
  excludeScope: 'localhost:4000',
  recorder: {
    enable_reqheaders_recording: true
  }
}, function() {
  it('works', function(done) {
    request('http://localhost:4000/users', function(err, res, body) {
      assert(!err, 'was success');
      done();
    });
  });

  describe('some other test', function() {
    // You can use mocha how you normally would to group tests
  });
});

Configuration

Defaults:

{
  // Don't record any requests to this scope
  // It can be an array or string
  excludeScope: ['localhost', '127.0.0.1', '0.0.0.0'],

  // Re-record and overwrite your current fixtures
  overwrite: false,

  // Record fixtures when test fails
  recordOnFailure: false,

  // These options are passed to the nock recorder that runs behind the scenes
  // to capture requests
  recorder: {
    output_objects:  true,
    dont_print:      true
  }
}

To overide these you can call describeFixture.setDefaults with an object to override them for ALL tests. It must be called before any describeFixture() is called to work properly. The best place is in a test helper file.

You also are able to pass in test specific options as the last parameter to describeFixture(). See the "Usage" section above for an example.

Authors

Versioning

This library follows Semantic Versioning

Want to help?

Please do! We are always looking to improve this library. If you have any ideas please open an issue or a pull requests and we'll work on getting them in.

Legal

Poetic Systems, Inc © 2014

@poeticsystems

Licensed under the MIT license