Quick answer: API scenario testing runs an ordered sequence of real, connected requests that model a business flow, where a value from one response can feed a later request and assertions run at every step. It verifies that the whole flow still works, instead of trusting a single endpoint response. The engine runs in the desktop main process, progress is streamed, and a run can be cancelled.
Why a single request is not enough
Hitting one endpoint and reading a 200 tells you very little about a real flow, because most business behavior spans several calls. A login returns a token, a second call uses it to create a resource, and a third reads it back.…