Mock calls dock

The Mock calls tab of the dock shows the requests the mock server receives while the scenario runs. It’s the reactive half of the Mock Studio: you see what your micros ask for and you complete it.

What it shows

A table with one line per call, like a browser inspector’s Network tab: status, method, path, the response that served it (with the rule that picked it, if any) and the time. The status comes first and in colour, and 4xx and 5xx rows get a marker on the left, so an error stands out without reading the row. Clicking a row opens it in the editor. You can:

• Filter by method or path.
• Group identical calls (with a ×N counter).
• See which variant responded to each one (or if there was no defined response).

From a call to a stub

When a call doesn’t have a defined response yet, you turn it into a stub with one click: Aseptic creates the endpoint in the Mocks section and takes you to edit it, without you having to search for it. It’s the flow that avoids the loop “look in logs → edit JSON by hand → relaunch”.

• Clear calls discards the observed ones.
• The mock URL button copies the mock server’s address to the clipboard.

See also

• Mocks section
• Mock a dependency without a cloud connection