Rodo NPM | npm.io

Rodo

HTTP mocking service

Rodo can be used to create a real mocked API with an specific port and host.

The main difference with other HTTP mocking libraries like nock is that Rodo creates a real HTTP server instead of overriding the behavior of Node HTTP objects.

Install

npm install rodo

Sample usage

Writing a new mocked endpoint can be as easy as:

// Mocking API
const assert = require('assert');
const rodo = require('rodo');
const mockServer = rodo(8000);
const myCall = mockServer
  .get('/foo')
  .reply({ bar: 'baz' })
  .withHeader('content-type', 'application/json');

// Action
const res = await fetch('http://localhost:8000/foo');
const json = await res.json();

// Assertions
assert.equal(json.bar, 'baz');
assert.equal(myCall.calls.length, 1);

Getting started

The request

To get started, you first need to instantiate the Rodo server doing the following:

const rodo = require('rodo');
const mockServer = rodo(8000);

Lets start building the filtering process for a specific request:

var myRequest = mockServer.request().havingMethod('GET').havingPath('/foo');

You can do the same by doing:

var myRequest = mockServer.get('/foo');

Nice! Now Rodo will intercept every request to GET http://localhost:8000/foo.

The response

Now you want Rodo to return a specific response to that request:

var myResponse = myRequest
  .reply()
  .withHeader('content-type', 'application/json')
  .withStatus(200)
  .withBody({ bar: 'baz' });

You can do the same with:

var myResponse = myRequest
  .reply({ bar: 'baz ' })
  .withHeader('content-type', 'application/json');

Good! you can now check for the requests that were resolved with that response:

myResponse.calls; // [...calls]

You are all set, now Rodo will start intercepting all that requests and will return the response that you specify.

If you now want to clear the results and start again

mockServer.clean();

If you now want to wait for all endpoints to be executed

mockServer.waitForPending();

Want to kill the server?

mockServer.close();

Extra server options

Aside from port and hostname, when instatiating the Rodo server you can optionally pass an object with any of these extra options:

Using multipart

Multipart will be handled using the multiparty library. An example for rodo handling multipart is:

mock
  .post('/foo')
  .havingFields({ bar: 'baz' })
  .havingFiles({
    quux: (file) => file.originalFilename === 'my-file.txt'
  })
  .reply('quux');

defaultResponseDelay

Instead of using .withDelay explicitly on each of your response methods, you can use this option to set a default delay that will be automatically applied to all of them. And if you have a case that needs a different value, you can still use .withDelay to overwrite the default.

API

Constructor

`rodo(port?, hostname?, options?)`

port: The port number of the server to be used by Rodo
hostname: Hostname of the server, if needed
options: Options for the server, options is an object with props, i.e.: { removeAfterUse: true }
- removeAfterUse: Remove call mocks after they are called
- cors: Enables CORS for every request