Bird
Raised Fist0
Postmantesting~20 mins

Collection runner results in Postman - Practice Problems & Coding Challenges

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Challenge - 5 Problems
🎖️
Collection Runner Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
query_result
intermediate
2:00remaining
What is the total number of requests run in this collection?
Given a collection runner result summary, determine the total number of requests executed.
Postman
SELECT COUNT(*) AS total_requests FROM collection_runner_results;
A20
B10
C15
D25
Attempts:
2 left
💡 Hint
Look for the total count of requests executed in the results table.
📝 Syntax
intermediate
2:00remaining
Identify the syntax error in this query to fetch failed requests
Find the syntax error in the following SQL query that tries to select all failed requests from collection runner results.
Postman
SELECT * FROM collection_runner_results WHERE status = 'failed';
ANo syntax error
BIncorrect table name
CMissing quotes around 'failed'
DMissing semicolon at the end
Attempts:
2 left
💡 Hint
Check if the query follows standard SQL syntax.
optimization
advanced
2:00remaining
Optimize this query to get average response time per request name
Given this query, choose the optimized version that efficiently calculates average response time grouped by request name.
Postman
SELECT request_name, AVG(response_time) FROM collection_runner_results GROUP BY request_name;
ASELECT request_name, AVG(response_time) FROM collection_runner_results GROUP BY request_name;
BSELECT request_name, SUM(response_time)/COUNT(*) FROM collection_runner_results GROUP BY request_name;
CSELECT request_name, MAX(response_time) FROM collection_runner_results GROUP BY request_name;
DSELECT request_name, AVG(response_time) FROM collection_runner_results;
Attempts:
2 left
💡 Hint
Use built-in aggregate functions with proper grouping.
🧠 Conceptual
advanced
2:00remaining
What does the 'iterations' field represent in collection runner results?
In the context of Postman collection runner results, what does the 'iterations' field represent?
ANumber of environments used
BNumber of requests in the collection
CNumber of failed requests
DNumber of times the entire collection was run
Attempts:
2 left
💡 Hint
Think about how many times the whole set of requests is executed.
🔧 Debug
expert
2:00remaining
Why does this query return zero rows when filtering by status 'passed'?
Given the query: SELECT * FROM collection_runner_results WHERE status = 'passed'; but it returns zero rows, what is the most likely cause?
Postman
SELECT * FROM collection_runner_results WHERE status = 'passed';
AThe table is empty
BThe status values are stored in uppercase like 'PASSED'
CThe column name is misspelled
DThe query syntax is invalid
Attempts:
2 left
💡 Hint
Check the exact stored values and case sensitivity.

Practice

(1/5)
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