Lab 02 - API Mocking

Return to Workshop

Lab 2

API Mocking

Bring your APIs to life

<img src=”../images/agenda-02.png “Login” width="900” />


When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.

Why Red Hat?

Red hat combines and number of commercial and Open Source tools to cover each part of the API Design lifecycle. In this lab we’ll be using the Microcks open source tool.

Lab Instructions

Prerequisite: Setup the collaboration environment using Git (Gogs)

For the Developer track, we require a collaboration environment based on Git. For this purpose, we decided to use Gogs which is a hosted, lighter-weight version of Gitlab. This lab environment has created a user for you in Gogs.

Follow this instructions to set up the repository.

  1. Open a browser window and navigate to gogs. Please ask your instructor if you need the link.

  2. Log into Gogs using your designated user and password. Click on Sign In.

    <img src=”../images/mock-01.png “Sign In” width="900” />

  3. In the main page, click in the + sign in the right top corner to display the New menu. Click the New Migration option.

    <img src=”../images/mock-02.png “New Migration” width="900” />

  4. Fill in the information of the repository migration with the following values:

    <img src=”../images/mock-03.png “New Migration Repository” width="900” />

  5. Click on Migrate Repository to fork the GitHub repo into Gogs.

  6. Switch to branch dev-track-lab-02

    <img src=”../images/mock-04.png “Upload File” width="900” />

  7. Open the locations-api folder and click on the filename link Locations-UserX.json to open and review the file.

    <img src=”../images/mock-05.png “Click File” width="900” />

  8. If everything is fine, click the Edit button to apply your personal user settings.

    <img src=”../images/mock-06.png “Edit file” width="900” />

  9. Replace UserX with your user number.

    <img src=”../images/mock-07.png “Rename file” width="900” />

  10. Commit the changes to gogs.

    <img src=”../images/mock-08.png “Commit file” width="900” />

  11. Click the RAW button to get the raw download version of the file.

    <img src=”../images/mock-09.png “Raw file” width="900” />

  12. Copy the browser tab URL. Store that URL address as you will use it in the next steps of the lab. The URL should look similar to the following:

    If you feel more comfortable, you can also copy and paste the RAW button link from the previous step. Also, don’t forget to update the X variable with your user number.

Step 1: Create a Microcks Job

  1. Open a browser window and navigate to microcks. Please ask your instructor if you need the link.

  2. Log in into Microcks using your designated user and password.

    <img src=”../images/mock-10.png “Openshift Login” width="900” />

  3. You are now in the main Microcks page. Click the Importers button to access the Importers page.

    <img src=”../images/mock-11.png “Job” width="900” />

  4. Click the Create button to create your first job.

    <img src=”../images/mock-12.png “Job” width="900” />

  5. In the Create a New Job dialog, type in the following information replacing X with your user number. Click Next.

    <img src=”../images/mock-13.png “Job Details” width="900” />

  6. Click Next for the Authentication options.

  7. Review the details and click on Create to create the job.

    <img src=”../images/mock-14.png “Create Job” width="900” />

  8. After your job is created, click on the Activate option.

    <img src=”../images/mock-15.png “Activate Job” width="900” />

  9. Repeat the last step, but now select the Force Import option. This will start the synchronization job.

    <img src=”../images/mock-16.png “Start Job” width="900” />

  10. Refresh your window to get it to the latest state.

  11. You will see 3 labels next to your Job. Click the Services label.

    <img src=”../images/mock-17.png “Job Services” width="900” />

  12. In the dialog you will see your service listed. Click on the Locations-UserX - 1.0.0. link.

    <img src=”../images/mock-18.png “Job Service” width="900” />

  13. Click Close to dismiss the dialog.

  14. This is your new REST mock service based on the OpenAPI definition you just loaded to Microcks. Click on the arrow to expand the GET /locations operation.

    <img src=”../images/mock-19.png “Mock Service” width="900” />

  15. You can check that the example we added to the definition in Lab 1 will be used to return the mock values. Scroll down, copy and save the Mocks URL, we will use that endpoint to test the REST mock service.

    <img src=”../images/mock-20.png “Mock Operation” width="900” />

Step 2: Test the REST Mock Service

We now have a working REST mock service listening for requests. We will use an online cURL tool to test it.

  1. Open a browser window and navigate to:
  2. Copy and paste the Mock URL from earlier step. Remember to replace X with your user number. It should look similar to the link below.
  3. Click the START YOUR CURL button.

    <img src=”../images/mock-21.png “cURL Service” width="900” />

  4. The page will load the response information from the service. You will be able to see the RESPONSE HEADERS and the actual RESPONSE_BODY. This last part contains the examples we add during the design phase.

    <img src=”../images/mock-22.png “cURL Response” width="900” />

Congratulations! You have successfully configure a Microcks Job to create a REST mock service to test your API.

Steps Beyond

So, you want more? …


In this lab you used Microcks to configure a REST mock service for the API definition you created in the previous lab. REST mock services allows you to simulate a REST API service when you are in a prototyping stage of your API program journey.

Microcks allows you to test a number of various responses for client application requests. When deploying API, micro-services or SOA practices at large scale, Microcks solves the problems of providing and sharing consistent documentation and mocks to the involved teams. It acts as a central repository and server that can be used for browsing but also by your Continuous Integration builds or pipelines.

Notes and Further Reading

Return to Workshop