Collection runner results in Postman

Introduction

Collection runner results show you the outcome of running a group of API requests together. They help you see which requests worked and which did not.

When you want to test multiple API requests in one go.

When you need to check if all parts of your API work correctly together.

When you want to save time by running many tests automatically.

When you want to see detailed results for each request in a collection.

When you want to export test results for sharing or analysis.

Syntax

Postman

No specific code syntax; collection runner results are shown in the Postman app interface or exported as JSON.

Results include status codes, response times, and test pass/fail info.

You can export results as a JSON file for further use.

Examples

This shows a summary of each request's status and test results.

Postman

Run a collection in Postman Collection Runner and view the results tab.

You get a JSON file with detailed info about each request's response and tests.

Postman

Export collection runner results as JSON from the Postman app.

Sample Program

This JSON shows results from running three API requests: Get, Update, and Delete user. Each request has its response code and test result.

Postman

{
  "run": {
    "stats": {
      "iterations": 1,
      "requests": 3,
      "tests": 3,
      "assertions": 3
    },
    "executions": [
      {
        "item": "Get User",
        "request": {
          "method": "GET",
          "url": "https://api.example.com/user/1"
        },
        "response": {
          "code": 200,
          "body": "{\"id\":1,\"name\":\"Alice\"}"
        },
        "tests": {
          "Status code is 200": true
        }
      },
      {
        "item": "Update User",
        "request": {
          "method": "PUT",
          "url": "https://api.example.com/user/1"
        },
        "response": {
          "code": 200,
          "body": "{\"id\":1,\"name\":\"Alice Updated\"}"
        },
        "tests": {
          "Status code is 200": true
        }
      },
      {
        "item": "Delete User",
        "request": {
          "method": "DELETE",
          "url": "https://api.example.com/user/1"
        },
        "response": {
          "code": 204,
          "body": ""
        },
        "tests": {
          "Status code is 204": true
        }
      }
    ]
  }
}

Important Notes

You can see how long each request took in the results.

Failed tests are clearly marked to help you fix issues.

Exported results can be used to create reports or share with teammates.

Summary

Collection runner results show the outcome of running many API requests together.

They include status codes, response bodies, and test pass/fail info.

You can view results in Postman or export them as JSON for sharing.

Practice

1. What information does the Postman Collection Runner primarily show after running a collection?

easy

A. The source code of the API server

B. Only the request URLs

C. Status codes, response bodies, and test pass/fail results

D. User login credentials

Solution

1. Step 1: Understand Collection Runner output

   The Collection Runner shows results of running multiple API requests together, including status codes, response bodies, and test results.

2. Step 2: Identify what is NOT shown

   It does not show server source code, only URLs, or user credentials.

3. Final Answer:

   Status codes, response bodies, and test pass/fail results -> Option C

4. Quick Check:

   Collection Runner output = status codes + responses + test results [OK]

Hint: Remember: Collection Runner shows results, not server code [OK]

Common Mistakes:

• Thinking it shows server source code
• Confusing request URLs with results
• Expecting user credentials in results

2. Which of the following is the correct way to export Collection Runner results in Postman?

easy

A. Click the 'Export Results' button after running the collection

B. Right-click the collection and select 'Export Results'

C. Use the Postman console to save results manually

D. Results cannot be exported from Postman

Solution

1. Step 1: Locate export option after running collection

   After running a collection in the Collection Runner, a button labeled 'Export Results' appears to save the run data.

2. Step 2: Confirm other options are incorrect

   Right-clicking the collection does not export results, console is for logs, and results can be exported.

3. Final Answer:

   Click the 'Export Results' button after running the collection -> Option A

4. Quick Check:

   Export button appears after run [OK]

Hint: Export results only after collection run completes [OK]

Common Mistakes:

• Trying to export before running collection
• Using console logs to export results
• Assuming export is unavailable

3. After running a collection with 3 requests, the Collection Runner shows these status codes: 200, 404, 200. What does this indicate?

medium

A. All requests succeeded

B. One request failed with 'Not Found' error

C. All requests failed

D. The collection did not run

Solution

1. Step 1: Interpret HTTP status codes

   Status code 200 means success; 404 means 'Not Found' error indicating failure for that request.

2. Step 2: Analyze the sequence of codes

   Two requests succeeded (200), one failed (404), so not all succeeded.

3. Final Answer:

   One request failed with 'Not Found' error -> Option B

4. Quick Check:

   200 = success, 404 = failure [OK]

Hint: 200 means success; 404 means resource missing [OK]

Common Mistakes:

• Assuming all requests succeeded
• Confusing 404 with success
• Ignoring mixed status codes

4. You ran a collection but the Collection Runner shows no results and an error message. What is the likely cause?

medium

A. Postman is offline or disconnected

B. The collection has no requests

C. You forgot to click the 'Run' button

D. The API server returned 500 errors

Solution

1. Step 1: Understand why no results appear

   If Postman is offline or disconnected, it cannot run requests, so no results show.

2. Step 2: Check other options

   Clicking 'Run' is required but error message suggests connection issue; empty collection or server errors still produce results.

3. Final Answer:

   Postman is offline or disconnected -> Option A

4. Quick Check:

   No results + error = connection problem [OK]

Hint: Check internet connection if no results appear [OK]

Common Mistakes:

• Assuming forgot to click run
• Thinking empty collection causes error
• Confusing server errors with no results

5. You want to share your Collection Runner results with a teammate. Which method ensures they see the exact test pass/fail details and response data?

hard

A. Copy only the request URLs and share

B. Take a screenshot of the Collection Runner window

C. Send the collection file without running it

D. Export the results as a JSON file and send it

Solution

1. Step 1: Identify how to share detailed results

   Exporting results as JSON includes all test pass/fail info and response data for exact sharing.

2. Step 2: Evaluate other options

   Screenshots may miss details, sending collection without run lacks results, URLs alone miss responses and tests.

3. Final Answer:

   Export the results as a JSON file and send it -> Option D

4. Quick Check:

   JSON export = full detailed results [OK]

Hint: Export results JSON for full detail sharing [OK]

Common Mistakes:

• Relying on screenshots only
• Sharing collection without results
• Sharing URLs without responses