Create an Isolated Environment with UP9 and Mocklab

UP9 enables developers to test mock services in an isolated environment without requiring expensive hardware resources, spinning up more containers, or risking broken changes caused by third party APIs.

Once you have installed and deployed UP9, generate traffic so UP9 can build skeleton test code. The more traffic, the more reliable and CI-ready the test code becomes. After UP9 has built your tests, mocks, and contracts, you're ready to mock a service within an isolated environment.

Once you have UP9 installed and observing service traffic, you can download a zip file that includes all of the tests, mocks, and contracts that belong to the current workspace.

Download Tests, Mocks and Contracts This is how the folder looks when opened:

[zipped folder]/
├── tests/
├── mocks/
└── contracts/

Tests, Mocks and Contracts Folder


The mocks folder includes mock configuration for all services that were observed in service traffic.

  • mockintosh.yml - main file with all mocked endpoints
  • mock-data - a directory that contains response payloads.
  • docker-compose.yml - Easy way to spin up all services as mocks

To run one or more of these mocks you can follow the instructions in Mocks under Developer Tools, or in the new open-source project, Mockintosh.

Mocks with Mocklab

Drag and drop your /wiremock folder to the stub importer in Mocklab. You now have your services ready to be deployed as mocks in an isolated environment, with very little work required on your part.


For support, feel free to use any one of the three: