scenario-mock-server v1.2.0

Scenario Mock Server

Mock server powered by scenarios.

Table of contents

• Scenario Mock Server
  • Table of contents
  • Installation
  • Example usage
  • Cookie mode
  • Allowing for multiple responses
  • Running tests in parallel
    • sms-scenario-id header
    • sms-context-id header
  • Additional API paths
    • /scenarios
    • /select-scenario
    • /groups
  • API
    • createExpressApp
    • run
      • scenarios
      • groups
      • options
  • Types
    • Mock
    • HttpMock
    • Response
    • HttpResponseFunction
    • GraphQlMock
      • Operation
    • GraphQlResponse
    • GraphQlResponseFunction

Installation

npm install scenario-mock-server

Example usage

const { run } = require('scenario-mock-server');

run({
	scenarios: {
		item: [
			{
				path: '/api/test-me',
				method: 'GET',
				response: { data: { blue: 'yoyo' } },
			},
		],
		cheese: [
			{
				path: '/api/test-me',
				method: 'GET',
				response: { data: { blue: 'cheese' } },
			},
		],
	},
});

Calls to http://localhost:3000/api/test-me will start by returning { blue: 'yoyo' }.

Visiting http://localhost:3000 will allow you to select a scenario. The first declared scenario will be initially selected. In this case, enabling cheese will modify /api/test-me so that it returns { blue: 'cheese' }.

Cookie mode

By default Scenario Mock Server runs in server mode storing the current selected scenario and context in server memory. Alternatively you can set cookieMode to true in the options, which stores the current scenario and context in a cookie instead. This is useful when you want to run a central mock server, but allow each user to select and store their own scenarios and associated contexts without it affecting other users.

Allowing for multiple responses

Sometimes you may want an endpoint to respond with different status codes depending on what is sent. It is the recommendation of this package that this can be achieved by using scenarios. However, given response can be a function, it is possible to respond with a different value for the status, headers, data and delay properties:

const mock = {
	path: '/some-path',
	method: 'GET',
	response: ({ body }) => {
		if (body.name === 'error1') {
			return {
				status: 400,
				data: { message: 'something went wrong' },
				delay: 1000,
			};
		}

		if (body.name === 'error2') {
			return {
				status: 500,
				data: { message: 'something else went wrong' },
				delay: 2000,
			};
		}

		if (body.name === 'notFound') {
			return {
				status: 404,
				data: { message: 'no data here' },
			};
		}

		// Default status is 200
		return { data: { message: 'success' } };
	},
};

Running tests in parallel

Scenario Mock Server aims for mock data to be readily available while you're devloping locally, but also when you're running your tests.

The default behaviour of Scenario Mock Server is to run with one scenario active at a time. However, this falls down if you want to use multiple scenarios at the same time when running your tests in parallel. This is where 2 custom headers will become useful: sms-scenario-id and sms-context-id.

Note: These headers are not currently supported in cookieMode.

sms-scenario-id header

When this header is set to the scenario id of choice, regardless of what the current scenario is set to in the server, all responses will behave as if this was the currently set scenario instead.

sms-context-id header

This header must also be set when context is being used, otherwise context will reset on each call to the server when using the sms-scenario-id header.

Additional API paths

In addition to responding to API requests as set up by the currently active scenario a few additional endpoints exist that return json:

• /scenarios
• /select-scenario
• /groups

These paths can be modified by using options (in case they clash with paths from scnearios).

/scenarios

Returns an array of scenarios available. Use GET.

type ApiScenario = {
	id: string;
	name: string;
	description: null | string;
	selected: boolean;
	group: null | string;
};

/select-scenario

Allows you to select which scenario is active. Use PUT and the following body:

{
	"scenarioId": "{SCENARIO_YOU_WANT_TO_SELECT}"
}

/groups

Returns an array of groups. Use GET.

type ApiGroup = {
	id: string;
	name: string;
};

API

createExpressApp

Returns the internal express instance.

function({ scenarios, options })

run

Returns an http server, with an additional kill method.

function({ scenarios, options })

scenarios

{ [scenarioId]: Array<Mock> | { name, description, context, mocks, extend, group } }

groups

{ [groupId]: groupName }

options

{ port, uiPath, selectScenarioPath, scenariosPath, groupsPath, cookieMode, parallelContextSize } | defaults to {}

Types

Mock

HttpMock | GraphQlMock

See HttpMock and GraphQlMock for more details.

HttpMock

{ path, method, response }

Response

{ status, headers, data, delay }

HttpResponseFunction

function({ query, body, params, headers, context, updateContext }): response | Promise<response>

GraphQlMock

{ path, method, operations }

Operation

{ type, name, response }

GraphQlResponse

{ status, headers, data, delay }

GraphQlResponseFunction

function({ variables, headers, context, updateContext }): response | Promise<response>