13 Collection Runner

title: "Collection Runner" description: "Run Postman collections with the Collection Runner for automated API testing. Learn run configuration, iteration settings, data files, delay configuration, and result analysis for manual and scheduled runs." weight: 13 date: 2026-06-28 lastmod: 2026-06-28 tags: [api-development, postman] }

The Collection Runner executes Postman collections with configurable iterations, data files, and delays. It provides a visual interface for running tests, viewing results, and exporting reports. Runners can be triggered manually or via Postman monitors.

What You'll Learn

• Collection Runner interface and settings
• Iteration and delay configuration
• Running with data files
• Result analysis and debugging
• Exporting run results

Why It Matters

The Collection Runner is the bridge between manual testing and automation. It lets you run all collection tests with one click and visualize results immediately.

Real-World Use

QA teams use the Collection Runner for regression testing before releases. Developers run collections to verify changes. Postman Monitors run collections on schedules for production health checks.

flowchart LR
    Runner[Collection Runner] --> Config[Run Configuration]
    Config --> Collection[Select Collection]
    Config --> Environment[Select Environment]
    Config --> Data[Data File]
    Config --> Iterations[Iteration Count]
    Config --> Delay[Delay Between Requests]
    Runner --> Results[Run Results]
    Results --> Pass[Pass Count]
    Results --> Fail[Fail Count]
    Results --> Logs[Console Logs]

Teacher Mindset

Run collections locally before pushing to CI. Use the runner to debug failures with visual feedback. Set appropriate delays to avoid rate limiting. Analyze failed iterations to find patterns.

Code Examples

// Example 1: Runner preparation script
// Add this as a collection pre-request to prepare for runner execution
pm.test('Runner setup check', () => {
    const baseUrl = pm.variables.get('base_url');
    pm.expect(baseUrl, 'Base URL must be set before running').to.not.be.empty;

    const authToken = pm.variables.get('auth_token');
    if (!authToken) {
        console.warn('No auth token found, login request will run first');
    }
});

// Log iteration info for debugging
console.log(`[${pm.info.counter}] Running: ${pm.info.requestName}`);

// Example 2: Result analysis in post-run
// After runner completes, analyze results programmatically
const results = {
    totalTests: pm.testRun.totalTests,
    passed: pm.testRun.passedTests,
    failed: pm.testRun.failedTests,
    duration: pm.testRun.duration
};

console.log(`Results: ${results.passed}/${results.totalTests} passed in ${results.duration}ms`);

// Identify failing tests
if (results.failed > 0) {
    pm.testRun.failures.forEach(failure => {
        console.error(`FAILED: ${failure.request.name} - ${failure.error.message}`);
    });
}

# Example 3: Running collections from command line
# Run with specific iterations
newman run collection.json \
  --environment staging.json \
  -n 3 \
  --delay-request 1000 \
  --timeout-request 5000

# Run with data file
newman run collection.json \
  -d test-data.csv \
  --reporters cli,json \
  --reporter-json-export ./results/run-results.json

Common Mistakes

• Running collections without the correct environment selected
• Setting iterations too high without data files (runs same data N times)
• Not setting delays between requests (may trigger rate limiting)
• Ignoring runner console logs for debugging failures
• Running the full collection when only specific tests need validation

Practice

1. Run a collection in the Collection Runner.
2. Configure iterations and delay settings.
3. Run with a data file and analyze iteration results.
4. Export the run results as a JSON report.
5. Challenge: Set up a Postman Monitor that runs the collection every hour and alerts on failures.

FAQ

Mini Project

Create a collection with 10 API tests. Run it in the Collection Runner with: 2 iterations with a data file containing 5 rows, 500ms delay between requests, and 'Stop on failure' disabled. Export the results as JSON and HTML. Analyze the results and identify any failures.

What's Next

Next, you will learn about Newman integration for CI/CD pipelines.