Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

stubborn-ws

Package Overview
Dependencies
Maintainers
1
Versions
53
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

stubborn-ws

[![Build Status](https://travis-ci.org/ybonnefond/stubborn.svg?branch=master)](https://travis-ci.org/ybonnefond/stubborn) [![Coverage Status](https://coveralls.io/repos/github/ybonnefond/stubborn/badge.svg?branch=master)](https://coveralls.io/github/ybonn

  • 1.1.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
1.4K
increased by4.34%
Maintainers
1
Weekly downloads
 
Created
Source

Stubborn

Build Status Coverage Status Greenkeeper badge

Stubborn web server to mock external api responses. It is basically nock meets Dyson. Stubborn will strictly match the requests based on the definition like nock but in a separate web server like Dyson.



Installation

Stubborn is tested on NodeJS 8.x and above.

Npm:

npm install --save-dev stubborn-ws

Yarn:

yarn add -D stubborn-ws

Usage

Stubborn is a testing tool that let you hot load and unload routes into a webserver. Requests are strictly matched against routes definitions based on Method, Path, Query parameters, Headers and Body. If the request does not exactly match one route definition (ex: extra parameter, missing parameter, value does not match, etc), Stubborn will respond with a 501.

The very fact that Stubborn respond to the request validates that the parameters sent are the expected one, any change in the code that send the request will break the test. Any breaking change will be picked up by your test.

Stubborn response headers and body can be hardcoded or defined using a template.

describe('Test', () => {
    const got = require('got');
    const { Stubborn } = require('stubborn-ws');

    const sb = new Stubborn();

    beforeAll(async() => await sb.start());
    afterAll(async() => await sb.stop());

    // Clean up all routes after a test if needed
    afterEach(() => sb.clear());

    it('should respond to query', async () => {
        const body = { some: 'body' };
        sb.get('/').setResponseBody({ some: 'body' });

        const res = await got(`${sb.getOrigin()}`, { json: true });

        expect(res.body).toEqual(body);
    });
});

Stubborn strictly matches the request against the route definition.

If a query parameter or a header is missing, stubborn will return a 501 (not implemented)

    it('should respond 501 if a parameter is missing', async () => {
        sb.get('/').setQueryParameters({ page: '1' });

        const res = await got(`${sb.getOrigin()}`, { throwHttpErrors: false });

        expect(res.statusCode).toEqual(501);
    });

If a query parameter or a header is added, stubborn will return a 501 (not implemented)

    it('should respond 501 if a parameter is added', async () => {
        sb.get('/').setQueryParameters({ page: '1' });

        const res = await got(`${sb.getOrigin()}?page=1&limit=10`, { throwHttpErrors: false });

        expect(res.statusCode).toEqual(501);
    });

If a query parameter or a header does not match the route definition, stubborn will return a 501 (not implemented)

    it('should respond 501 if a parameter does not match the definition', async () => {
        sb.get('/').setQueryParameters({ page: '1' });

        const res = await got(`${sb.getOrigin()}?page=2`, { throwHttpErrors: false });

        expect(res.statusCode).toEqual(501);
    });

You can use null as wildcard

    it('should respond using wildcard', async () => {
        sb.get('/')
            .setQueryParameters({ page: null })
            .setHeaders(null);


        const res = await got(
            `${sb.getOrigin()}?page=2`, 
            { 
                headers: { 'x-api-key': 'api key', 'any-other-header': 'stuff' }, 
                throwHttpErrors: false 
            }
        );

        expect(res.statusCode).toEqual(200);
    });

API

See the API documentation

Contributing

Release

git checkout master
git pull --rebase
yarn doc
git add .
git commit -m 'doc(): Update documentation'
yarn publish --<major|minor|patch>
git push --follow-tags

Then go to github to draft a new release

Keywords

FAQs

Package last updated on 29 Nov 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc