Why mocking enables parallel development in Postman - Test Execution Impact

Test Overview

This test checks how mocking an API in Postman allows frontend and backend teams to work at the same time without waiting for the real API to be ready.

Test Code - Postman Test Script

Postman

pm.test("Mock API returns expected data", function () {
    pm.response.to.have.status(200);
    const jsonData = pm.response.json();
    pm.expect(jsonData).to.have.property('userId');
    pm.expect(jsonData.userId).to.eql(1);
});

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts by sending a request to the mocked API endpoint in Postman.	Postman sends request to mock server URL, which returns predefined JSON data.	-	PASS
2	Postman receives response with status 200 and JSON body containing userId = 1.	Response visible in Postman with status 200 and body {"userId":1}.	Check response status is 200.	PASS
3	Test script parses JSON response and checks if 'userId' property exists.	JSON parsed successfully from response body.	Verify response JSON has property 'userId'.	PASS
4	Test script asserts that 'userId' equals 1 as defined in the mock.	Value of userId is 1 as expected.	Assert userId === 1.	PASS
5	Test completes successfully, confirming mock API behaves as expected.	Test report shows all assertions passed.	-	PASS

Failure Scenario

Failing Condition: Mock API returns incorrect data or is not reachable.

Execution Trace Quiz - 3 Questions

What does the test verify about the mock API response?

A It modifies the userId value dynamically.

B It connects to the real backend server.

C It returns status 200 and userId equals 1.

D It returns an error status.

Key Result

Mocking APIs allows frontend and backend teams to develop and test independently by simulating expected responses, speeding up the overall development process.