Typical CLI flows

Launch a scenario and test it (agent / CI)

microlab start "Order checkout" --json   # starts Docker if needed and waits healthy
microlab status --json                     # effective URLs of each micro
# ... test HTTP calls against those URLs ...
microlab stop
microlab daemon stop

start already starts Docker on its own. If your CI brings it up externally, add --no-docker.

Define a mock and verify it

microlab mock operations catalog-core
microlab mock skeleton catalog-core GET /catalog/api/v1/scopes > body.json
microlab mock save catalog-core --data '{"method":"GET","pathPrefix":"/catalog/api/v1/scopes","active":0,"variants":[{"label":"200","status":200,"jsonBody":[]}]}'
microlab mock probe GET /catalog/api/v1/scopes

Share a scenario

microlab scenario export "Order checkout" --include-run
# (send the .microlab.yml) ... and on the other machine:
microlab scenario import order-checkout.microlab.yml            # see plan
microlab scenario import order-checkout.microlab.yml --apply --mocks union

Debug a failing micro

microlab status
microlab logs orders-core -n 500
microlab logs --errors
microlab restart orders-core
microlab logs orders-core -f

See also

• Commands by group · Debug a micro that won’t start