Note: Collection Runs require Advanced Mode. Enable it via Settings → Advanced Mode checkbox.

COLLECTIONS

Collection Runs

Execute all requests in a collection in one click — sequentially for chaining or in parallel for speed. View live progress, results, and export HTML reports.

Overview

Collection runs let you execute every request in a collection with a single action, ideal for integration testing, smoke tests, and automated workflows.

Run all requests in a collection with one click

Available from Collection Editor → Runs tab (Advanced Mode)

Also available via CLI: openpost run "Collection Name"

Full pipeline per request: auth, scripts, cookies, testRules, setVariables, history

Digest auth retry handled per-request

Sequential Mode

Requests execute one after another in array order, sharing a single environment context. This enables powerful variable chaining between requests.

Requests execute one after another in array order

Shared environment context: variables set by request N are available to request N+1

Enables chaining: extract token from login → use in subsequent requests

Script execution: collection scripts + folder scripts + request scripts all run

Failure in one request does NOT stop the run — all requests execute regardless

💡 Tip: Use sequential mode when requests depend on each other — for example, a login request that sets a {{token}} variable used by all subsequent requests.

Parallel Mode

Requests execute concurrently for faster completion. Each request gets its own isolated copy of environment variables — no cross-request state leakage.

Requests execute concurrently with configurable concurrency (e.g., 5 at a time)

Each request gets a separate copy of environment variables (no chaining)

Faster for independent requests (health checks, smoke tests)

Concurrency slider: 1–50 concurrent requests

Feature	Sequential	Parallel
Execution	One at a time, in order	N at a time, concurrent
Variable sharing	Shared — chaining works	Isolated — no chaining
Best for	Dependent workflows	Independent smoke tests
Speed	Slower (serial)	Faster (concurrent)

Progress & Results

During execution, a live progress bar tracks completion. After the run, a detailed results table shows the outcome for each request.

Live progress bar during execution

Results table: method, name/URL, status code, response time, test pass/fail

Click a result row to see full response details

Row color coding:

Green — All tests passed Red — Test failures Yellow — No tests defined

Summary bar: Total requests, passed count, failed count, and total execution time displayed at the top of the results.

HTML Reports

Export your run results as a standalone HTML report — self-contained with no external dependencies, ready to share or archive.

Export results as a standalone HTML report

Includes: run metadata, per-request results, test outcomes, timing

Self-contained file (no external dependencies)

Useful for CI/CD artifacts, stakeholder sharing, compliance records

Export button appears after a run completes

Click the export button after a run to generate the HTML report

CLI Runs

Run collections from the terminal for CI/CD integration, scripted workflows, or headless testing.

openpost run "Collection Name" --env production
openpost run "Collection Name" --mode parallel --concurrency 10
openpost run "Collection Name" --filter "GET*"
openpost run "Collection Name" --output-file results.json

Flag	Description
--env	Environment name to activate
--mode	`sequential` or `parallel`
--concurrency	Number of concurrent requests (parallel mode)
--filter	Glob pattern to run a subset of requests
--output-file	Write results to JSON file for CI integration

Exit codes:

0 — All tests passed 1 — Test failures 2 — Execution error

See the CLI documentation for full reference.

Variables & Chaining

In sequential mode, variables extracted by one request are immediately available to subsequent requests — enabling powerful multi-step workflows.

Sequential mode: setVariables from request N saved to env, available in request N+1

Common pattern: POST /auth/login extracts token → GET /users uses {{token}}

Collection variables available to all requests

Vault secrets resolved per-request

Parallel mode: each request starts with a fresh copy (no cross-request state)

Example chaining workflow:

1. POST /auth/login        → setVariable: token = $.access_token
2. GET  /users             → uses {{token}} in Authorization header
3. POST /users/{{userId}}  → uses {{userId}} from step 2 response

Import & Export → CLI Runs →