Typical CLI flows

Launch a scenario and test it (agent / CI)

aseptic start "Order checkout" --json   # starts Docker if needed and waits healthy
aseptic status --json                     # effective URLs of each micro
# ... test HTTP calls against those URLs ...
aseptic stop
aseptic 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

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

Share a scenario

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

Debug a failing micro

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

See also

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