Scenario
A scenario is a set of micros that are launched together to test a complete flow (for example, “Order checkout”). It’s the unit you work with: you compose it once and launch it whenever you want.
What a scenario stores
Section titled “What a scenario stores”- Which micros make it up.
- How each dependency between them is resolved: local, cloud or mock.
- Each micro’s mode: native or container.
What you choose in the app is saved in the scenario itself
(.microlab/scenarios/<name>.yml, versionable). The one-off tweaks you make “just for
this time” (a temporary override of resolution or mode) are remembered by the app in its
runtime state, without cluttering the saved scenario.
Composing a scenario
Section titled “Composing a scenario”In the Scenarios section, “New scenario” opens the editor: you give it a name and check the micros. Once created, you have four views of the active scenario —cards, table, call graph and dependencies panel— and the top bar to start it, stop it, clean it or edit it.
Lifecycle
Section titled “Lifecycle”Launching a scenario (▶) starts the infrastructure, resolves the ports, rewrites the URLs between micros and starts each one. Stopping it (■) stops micros, containers and infrastructure. See Your first scenario.
Sharing
Section titled “Sharing”A scenario can be exported to a self-contained file and imported on another machine, with conflict reconciliation. See Share a scenario.