Why running collections validates flows in Postman - Test Execution Impact

Test Overview

This test runs a Postman collection to check if the API flows work correctly end-to-end. It verifies that each request gets the expected response and that the sequence of calls behaves as planned.

Test Code - Postman Tests

Postman

pm.test('Status code is 200', function () {
    pm.response.to.have.status(200);
});

pm.test('Response has expected property', function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData).to.have.property('id');
});

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test runner starts and loads the Postman collection	Postman app is open with the collection loaded	-	PASS
2	Runner sends the first API request in the collection	Request sent to API server, waiting for response	-	PASS
3	Runner receives response with status 200	Response received with JSON body	Check if status code is 200	PASS
4	Runner executes test script to verify response body has 'id' property	Response JSON parsed	Verify response JSON contains 'id' property	PASS
5	Runner proceeds to next request in the collection	Next request prepared with data from previous response if needed	-	PASS
6	Runner completes all requests and tests in the collection	All requests executed, all tests passed	All test assertions passed for each request	PASS

Failure Scenario

Failing Condition: API response status is not 200 or expected property missing in response

Execution Trace Quiz - 3 Questions

What does the test check after receiving the API response?

A That the status code is 200

B That the response time is less than 1 second

C That the server is running on port 8080

D That the request method is POST

Key Result

Running a collection validates flows by checking each API response and its data step-by-step, ensuring the entire sequence works as expected.