Challenge Overview
Challenge objectives
-
Create mock endpoints on the provided source code based on the provided Swagger definition (attached on the challenge forum).
Project background
Our client Redwood has provided us with a set of Swagger definition files describing the APIs used by their application named “Bluesource”.
As part of this challenge series, we will create mock implementation of those APIs that we will then use to run their frontend app (Bluesource).
Tech stack
-
Node.js
-
Swagger
Code access
Repo: https://github.com/tc-bluesource/mock-api
Branch: develop
You will find a link to get access to the repo on the challenge forum.
Detailed requirements
You will find a Swagger definition attached on the challenge forum. We need your help to mock all endpoints described in the swagger definition so we can use the mock API during our frontend development.
As part of this challenge, you need to:
-
You need to mock all endpoints from the provided Swagger definition.
-
All mock data should be stored in JSON files.
-
All mock data should look realistic. Do not just use “lorem ipsum”. You may use packages like faker to generate the mock data.
-
You only need to cover the responses with status codes: 200/201/401. Other responses are not needed.
-
All mock services should be placed on a file inside the /services directory named producer-microservice-api.js
-
Only the endpoints with the provided tags (see forum) are in the scope of this challenge.
Feel free to post any questions on the challenge forum!
What to submit
-
Submit a git patch for the latest commit in the develop branch.