0.7.0 • Published 5 years ago

@dringtech/openapi-stubber v0.7.0

Weekly downloads
1
License
ISC
Repository
-
Last release
5 years ago

openapi-stubber

Build Status Mutation testing badge

Auto-stubbing for OpenAPI V3 specs

This is a utility wrapper around openapi-backend aimed at rapidly standing up a stub server, primarily for testing purposes.

Installation

npm install --save-dev @dringtech/openapi-stubber

Usage

The loadStub and tearDown functions each return a promise, so can work nicely with async code.

Load the required stubs before running tests (or whenever).

const stubber = require('@dringtech/openapi-stubber');

await stubber.loadStub({
  name: 'Stub Name',
  spec: SPEC_DEF,
  port: 8000,
  stack: STACK,
  overrides: OVERRIDES,
  fixtures: FIXTURES,
  validateRequests: true|false
});

The spec (SPEC_DEF) can be anything that openapi-backend understands, primarily:

  • Path to an OpenAPI V3 file
  • An OpenAPI spec object

It is also possible to pass an optional overrides property to the loadStub call. This allows control over the example returned in response to a given path. The format is

{
  '/path/to/override': 'NameOfExampleInOpenAPISpec',
}

The examples must be defined in the OpenAPI Spec document.

Additional stack handling (e.g. setting headers) can be performed by passing in a stack property to the options. This must be a valid express middleware stack definition: either a single function with the signature (req, res, next), or an array of such functions.

Fixtures, over and above that supported by the OpenAPI examples, can be specified in the fixtures property. A full example of this is given below:

{
  '/path/to/override': {
    status: 'HTTP STATUS CODE',
    mock: 'DATA TO RETURN FROM CALL TO PATH',
    contentType: 'CONTENT TYPE TO SET'
  }
}

Only the mock property is required. status defaults to 200 and contentType defaults to application/json.

Requests to the stub backend will be validated by default. To override this behaviour, set the validateRequests property to false.

Once the tests (or whatever) are completed call the following code to clean up:

await stubber.tearDown();

Logging

If you want to log the stub output, call the following before any stubs are loaded:

stubber.setupLogging({ logFile: '/path/to/log/file.log' });
0.7.0

5 years ago

0.6.0

5 years ago

0.5.0

5 years ago

0.4.0

5 years ago

0.3.0

5 years ago

0.2.0

5 years ago

0.1.0

5 years ago