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

mocr

v0.6.0

Published

A mock http server used in tests

Downloads

6

Readme

mocr npm github-ci

A mock http server used in tests

Features

  • Easy to use, mock http server
  • Spy/track requests received by the server
  • Designed to work with end-to-end & unit tests
  • Strongly typed, types included
  • Zero dependencies

Installation

yarn add -D mocr
# or
npm install --save-dev mocr

Configuration

All config options mentioned below are optional.

| Name | Default | Description | | ----- | ------- | ------------------------------------------ | | debug | false | When set to true, logging will be enabled. | | port | 9091 | The port that the server will be running. |

Usage

import mocr, { createRequestSpy } from 'mocr';

describe('my tests', () => {
  const mockServer = mocr({
    /* Configuration */
  });

  beforeAll(async () => {
    // Start the server
    await mockServer.start();
  });

  beforeEach(async () => {
    // Reset the request spy
    mockServer.requestSpy.reset();
  });

  afterAll(async () => {
    // Stop the server
    await mockServer.stop();
  });

  it('should make a call to the backend when pressing the button', () => {
    // Press the button

    const { request, body } = requestSpy.calls[0];

    expect(mockServer.requestSpy).toHaveBeenCalledTimes(1);
    expect(request.method).toBe(/* Expected Method, ie. POST, PUT */);
    expect(body).toHaveBeenCalledWith(/* Expected Request Body */);
  });
});

Methods

mocr

const mockServer = mocr(/* Optional Config */);

await mockServer.start();
// Run your test case
await mockServer.stop();

Used to create an instance of mocr - it accepts optional configuration. You can have as many mocr servers running in parallel as long as they run on a different port. See example for a complete example.

start()

const mockServer = mocr(/* Optional Config */);

await mockServer.start();

Starts the http server.

stop()

const mockServer = mocr(/* Optional Config */);

await mockServer.stop();

Stops the server of the mocr instance.

mockNextResponse({ data })

const { start, stop, mockNextResponse } = mocr(/* Optional Config */);

mockNextResponse({ foo: 'bar' });

Used to return a mock/stubbed response from the server. Will only use that response once and will then fall back to the default Hello World server response. For mocking multiple requests, see mockNextResponses below.

mockNextResponses([ { data } ])

const { start, stop, mockNextResponses } = mocr(/* Optional Config */);

mockNextResponses([{ id: '123' }, { id: '456' }]);

Similar to mockNextResponse but expects an array of data. The data will be return for each response in the order they appear in the array.

Properties

requestSpy

const { start, stop, requestSpy } = mocr(/* Optional Config */);

expect(requestSpy.calls).toHaveLength(1);

Holds a records/tracks all incoming requests to the mock server along with their body/data(if any). To be used for validating requests/content leaving your application. Below you can find all available methods for a RequestSpy. See example above.

| Name | Description | | ----- | ----------------------------------------------------------------------------- | | calls | An array of all the calls. [ {request: IncomingMessage. body: string {} } ] | | reset | Empties the calls array. |

License

This project is licensed under the MIT License - see the LICENSE file for details