Skip to content
MicroLab MicroLab

Your first scenario in 5 minutes

This tutorial takes you from zero to a running scenario. A scenario is a set of micros that are launched together to test a flow (for example, “Order checkout”).

1. Add your micros

Section titled “1. Add your micros”

In the left rail, go to Micros and click + Add micro. Choose the folder of a micro’s repository: MicroLab autodetects its technology, ports, infrastructure and dependencies, and generates its description (the manifest). Repeat it for each micro you want to use.

Is the repo on a Git server and you don’t have it locally yet? Use Import micro from Git: it clones the repository and detects the micro in one step.

2. Compose the scenario

Section titled “2. Compose the scenario”

Go to the Scenarios section and click New scenario. Name it and check the micros that make it up. Save it.

In the Dependencies panel you’ll see, for each call from one micro to another core, how it is resolved. For each dependency you choose:

  • local — points to the peer launched in the same scenario (test the real communication between your micros).
  • cloud — points to the DEV environment (may require VPN).
  • mock — points to MicroLab’s mock server (work without VPN or launching the core).

Detail in Dependencies.

3. Check the environment

Section titled “3. Check the environment”

Before launching anything, open the Environment check (right rail). It tells you whether you have what you need —tools, repositories, Docker, databases, credentials— before discovering it with a failure mid-launch. Warnings don’t block; failures do.

4. Launch the scenario

Section titled “4. Launch the scenario”

Make sure Docker is started (Docker section of the right rail) and click ▶ Start in the top bar. MicroLab launches the infrastructure, resolves the ports, rewrites the URLs between micros and starts each one. Each micro goes from Stopped → Starting → Healthy.

5. Observe and test

Section titled “5. Observe and test”

With the scenario running, the bottom dock gives you:

  • Logs — live, filterable by micro and by level.
  • Mock calls — what the mocks receive (with the option to turn a call into a stub).
  • Status — CPU, memory and logs charts per micro.

In the scenario’s Table or Cards view you have, per micro, its status, port and shortcuts (open Swagger/health, copy URL, view logs, restart just that micro).

6. Stop when you’re done

Section titled “6. Stop when you’re done”

Click ■ Stop. MicroLab stops the micros, the containers and the infrastructure.

And now

Section titled “And now”