Topic
The create call returned 200, the detail view 404s, and cancel accepts an illegal state. Scenario tests chain real calls, pass data between steps, and hand the agent evidence to fix with.
Read articleA folder of requests that each return 200 is not a test suite. A scenario chains requests the way a user walks the product: create, capture, poll, act, assert. Here is how to derive scenarios from an OpenAPI spec and run them against mock then staging.
Read articleWe pointed Prism, Microcks, Postman mock servers, and a local spec-driven workspace at the same OpenAPI 3.2 document, including an SSE stream. Here is what each handled, what cost money, and where examples quietly became lies.
Read articleA concrete sprint diary: one OpenAPI file drove a local mock with latency and error overrides, a four-step checkout scenario with an HTML report, live docs, derived database tables and a hosted MCP endpoint while the real API did not exist yet.
Read articleWebSocket testing breaks every habit from REST: the handshake is HTTP but everything after is framed and bidirectional, auth happens at upgrade time or immediately after, and correctness means message sequences. Here is a practical testing workflow from wscat to CI scenarios.
Read articleSSE looks like HTTP until you try to test it: the connection stays open, events have names and ids, heartbeats hide disconnects, and ordinary API clients hang. Here is how to test streams with curl, what Postman does and does not do, and how to make SSE scenarios repeatable from an OpenAPI spec.
Read article