Collection Runner

Automate API testing by running entire collections

Overview

The Collection Runner allows you to execute all requests in a collection sequentially with a single click. Perfect for automated testing, load testing, and continuous integration workflows.

Collection Runner Collection API Test Suite (12 requests) Configuration Environment: Production Iterations: 10 Delay (ms): 1000 Requests (12) GET /api/users POST /api/users GET /api/users/:id Run Collection
Powerful Automation: Run hundreds of requests with environment variables and CSV data files!

Key Features

Sequential Execution

Runs all requests in order automatically

Environment Support

Use environment variables for different setups

Data-Driven Testing

Load data from CSV/TXT files for iterations

Multiple Iterations

Run collection multiple times

Delay Between Requests

Configure wait time between requests

Detailed Results

View comprehensive results and statistics

Running a Collection

Open Collection Runner

Click the "Collection Runner" tab in the main interface.

Select Collection

Choose a collection from your sidebar or upload a JSON file.

Select Collection Choose from collections... API Test Suite (12 requests) User Management (8 requests) ✓ Authentication (5 requests)

Configure Run Settings

  • Environment: Select environment (optional)
  • Iterations: Number of times to run (default: 1)
  • Delay: Wait time between requests (ms)
Configuration Settings Environment: Production Iterations: 1 10 Delay (ms): 1000 Save responses Configuration complete!

Click "Run Collection"

Click the Run Collection" button to start execution.

View Progress

Watch requests execute in real-time with live progress bar.

Running: User Management Collection Progress: 75% (6/8) Complete! (8/8) GET /users - 200 OK (123ms) POST /users - 201 Created (245ms) GET /users/123 - Running... GET /users/123 - 200 OK (98ms)

View Results

See detailed results with pass/fail status for each request.

Run Complete: 8/8 Passed 0 Failed 1.2s REQUEST STATUS TIME TESTS GET /users 200 OK 145ms 3/3 POST /users 201 Created 234ms 2/2 GET /users/123 200 OK 98ms 4/4 Summary Total Requests: 8 Passed: 8 Failed: 0 Total Time: 1.2s

Data-Driven Testing

Run your collection with different data for each iteration using CSV or TXT files:

Preparing Data File

Create a CSV file with your test data:

username,email,role
john_doe,john@example.com,admin
jane_smith,jane@example.com,user
bob_jones,bob@example.com,manager

Using Data Variables

Upload Data File

In Collection Runner, click "Upload Data File" and select your CSV.

Data File Configuration Drop CSV file here or click to browse users_data.csv 50 rows detected ✓

Use Variables in Requests

Reference CSV columns in your requests:

POST {{baseUrl}}/users
Body:
{
  "username": "{{username}}",
  "email": "{{email}}",
  "role": "{{role}}"
}

Run Collection

Collection runs once for each row in your CSV!

Data-Driven Execution: 50 Iterations Progress: Iteration 35/50 Complete: 50/50 Iterations Recent Iterations: Iteration 33: user_alice@test.com - All tests passed Iteration 34: user_bob@test.com - All tests passed Iteration 35: user_carol@test.com - Running... Iteration 35: user_carol@test.com - All tests passed Each iteration uses different data from CSV row
Automatic Iterations: With 3 rows in CSV, collection runs 3 times with different data each time!

Understanding Results

Summary Statistics

At the top of results, you'll see:

Run Summary 8 Total Requests Executed 8 ✓ Passed 100% Success 0 Failed No Errors 1.2s Total Time Avg: 150ms

Individual Request Results

For each request, view:

Detailed Request Results GET /api/users 200 OK Response Time: 145ms Tests Passed: ✓ 3/3 Response Size: 2.4 KB POST /api/users 201 Response Time: 234ms Tests Passed: ✓ 2/2 Response Size: 1.8 KB Request Body: {"name": "John", "email": "john@test.com"}

Expanding Results

Click any request to see:

Common Use Cases

1. Smoke Testing

Verify all endpoints are responding:

Iterations: 1
Delay: 0ms
Result: Quick health check

2. Integration Testing

Test complete user flows:

1. Login
2. Get Profile
3. Update Profile
4. Logout

3. Load Testing

Stress test with iterations:

Iterations: 1000
Delay: 100ms
With dynamic variables

4. Data Migration

Bulk import from CSV:

CSV: 500 users
Iterations: auto
Create all users

5. Regression Testing

Test after code changes:

Run full test suite
Verify no breakage
CI/CD integration

6. Multi-Environment

Test across environments:

Run with Dev env
Run with Staging env
Run with Prod env

Best Practices

1. Add Test Scripts

Validate responses with test assertions for automatic pass/fail detection.

2. Use Delays

Add delays between requests to avoid overwhelming servers.

3. Organize Collections

Keep related requests together in logical order.

4. Use Variables

Leverage environment and data variables for flexibility.

5. Start Small

Test with few iterations first, then scale up.

6. Monitor Results

Review detailed results to identify issues quickly.

Advanced Features

Collection Scripts

Run scripts before/after every request in collection:

// Collection Pre-request Script
rm.environment.set("timestamp", Date.now());
console.log("Starting request at:", new Date());

// Collection Test Script
rm.test("Response time acceptable", function() {
    rm.expect(rm.response.responseTime).to.be.below(1000);
});

Chaining Requests

Use test scripts to pass data between requests:

// Request 1: Login
const response = rm.response.json();
rm.environment.set("authToken", response.token);

// Request 2: Get Profile (uses authToken)

Conditional Execution

Skip requests based on conditions:

// In Pre-request Script
if (rm.environment.get("skipAdmin") === "true") {
    rm.skipRequest();
}

Exporting Results

Save run results for documentation or reporting:

Complete Run

Finish running your collection.

Click "Export Results"

Find the export button in the results panel.

Choose Format

  • JSON: Complete data for programmatic use
  • HTML: Beautiful report for sharing
  • CSV: Import into Excel/Sheets
📤 Export Results Export Format: ⚫ JSON (Detailed) ○ CSV (Summary) Include: ✓ Request details ✓ Test results Cancel Export