Collection runner

The collection runner executes every HTTP request under a folder (or the whole workspace) in order — useful for smoke tests, seeding data, and end-to-end flows.

Running requests

To start a run, trigger the collection runner from the sidebar. It will sequentially execute all HTTP requests in your selected folder. Note that WebSocket, SSE, gRPC, and MCP requests are currently skipped during a collection run.

Chaining and iteration

You can chain requests together by passing values between them. Use the im.environment.set() function in your test scripts to store a value from one response and use it in a subsequent request.

For data-driven testing, the runner supports data-file iteration. You can upload a CSV or JSON file, and the runner will repeat the folder’s sequence for each row in your dataset.

Results and controls

The runner provides an aggregated view of your test results, showing passes and failures across the entire run. You can configure a delay between requests to avoid rate limits and, if necessary, cancel an in-flight run at any time.

Run report

When a run finishes, a summary strip shows the outcome at a glance: requests that succeeded, the test pass rate, total wall-clock time, and the average request time (plus whether the run was cancelled). Failed tests can be expanded for details.

Click Download report to save the run as a self-contained HTML file — no external assets, so it can be attached to a ticket or shared with the team as-is.