Why response validation confirms correctness in Postman - Test Execution Impact

Test Overview

This test sends a request to an API endpoint and checks the response status and body content. It verifies that the API returns the expected data, confirming the correctness of the response.

Test Code - Postman Tests

Postman

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

pm.test("Response has expected user name", function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData.name).to.eql("John Doe");
});

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	Send GET request to API endpoint /users/123	Postman sends HTTP GET request to the server	—	PASS
2	Receive HTTP response from server	Response received with status code 200 and JSON body	—	PASS
3	Check if response status code is 200	Response status code is 200 OK	pm.response.to.have.status(200)	PASS
4	Parse response JSON and check if 'name' field equals 'John Doe'	Response JSON contains {"name": "John Doe", ...}	pm.expect(jsonData.name).to.eql("John Doe")	PASS

Failure Scenario

Failing Condition: Response status code is not 200 or 'name' field does not match 'John Doe'

Execution Trace Quiz - 3 Questions

What does the test check first after receiving the response?

A If the status code is 200

B If the response time is less than 1 second

C If the response body is empty

D If the server is reachable

Key Result

Validating both the response status code and key response data ensures the API behaves correctly and returns expected results, which confirms the correctness of the response.

Practice

1. Why is response validation important in Postman testing?

easy

A. It deletes unnecessary data from the server

B. It speeds up the API response time

C. It changes the API response data

D. It confirms the system returns the correct and expected data

Solution

1. Step 1: Understand the purpose of response validation

   Response validation checks if the API returns the data we expect, ensuring correctness.

2. Step 2: Identify the correct role of response validation

   It does not change or speed up data but confirms correctness and reliability.

3. Final Answer:

   It confirms the system returns the correct and expected data -> Option D

4. Quick Check:

   Response validation = correctness check [OK]

Hint: Response validation checks correctness, not speed or data change [OK]

Common Mistakes:

• Thinking validation changes data
• Confusing validation with performance improvement
• Assuming validation deletes data

2. Which Postman test code correctly checks if the response status is 200?

easy

A. pm.test('Status is 200', () => pm.response.status(200));

B. pm.test('Status is 200', () => pm.response.to.have.status(200));

C. pm.test('Status is 200', () => pm.response.statusCode == 200);

D. pm.test('Status is 200', () => pm.response.checkStatus(200));

Solution

1. Step 1: Review Postman syntax for status code check

   The correct method is pm.response.to.have.status(200) inside pm.test.

2. Step 2: Identify incorrect syntax

   Options B, C, and D use invalid or unsupported methods for status checking.

3. Final Answer:

   pm.test('Status is 200', () => pm.response.to.have.status(200)); -> Option B

4. Quick Check:

   Correct syntax uses .to.have.status() [OK]

Hint: Use pm.response.to.have.status(200) for status checks [OK]

Common Mistakes:

• Using pm.response.status(200) which is invalid
• Using equality check without pm.test
• Calling non-existent methods like checkStatus

3. Given this Postman test code, what will be the test result if the response status is 404?

pm.test('Check status', () => {
  pm.response.to.have.status(200);
});

medium

A. Test passes because status 404 is close to 200

B. Test throws a syntax error

C. Test fails because status is not 200

D. Test passes but with a warning

Solution

1. Step 1: Understand the test condition

   The test expects the response status to be exactly 200.

2. Step 2: Compare actual status with expected

   The actual status is 404, which does not match 200, so the test fails.

3. Final Answer:

   Test fails because status is not 200 -> Option C

4. Quick Check:

   Status 404 != 200 means test fail [OK]

Hint: Exact status match needed; 404 ≠ 200 means fail [OK]

Common Mistakes:

• Assuming close status codes pass
• Expecting syntax error instead of fail
• Thinking warnings occur on mismatch

4. Identify the error in this Postman test code that checks if the response JSON has a 'name' field:

pm.test('Check name field', () => {
  pm.expect(pm.response.json().name).to.equal;
});

medium

A. Missing value in to.equal assertion

B. Incorrect method pm.response.json() usage

C. pm.expect should be pm.test

D. No error, code is correct

Solution

1. Step 1: Analyze the assertion syntax

   to.equal requires a value to compare against, but none is provided here.

2. Step 2: Confirm other parts are correct

   pm.response.json() is valid, and pm.expect is correct for assertions.

3. Final Answer:

   Missing value in to.equal assertion -> Option A

4. Quick Check:

   to.equal needs a value to compare [OK]

Hint: Always provide a value inside to.equal() [OK]

Common Mistakes:

• Leaving to.equal empty
• Confusing pm.expect with pm.test
• Misusing pm.response.json()

5. You want to confirm that the API response contains a 'status' field with value 'success' and the response time is less than 500ms. Which Postman test code correctly validates both conditions?

hard

A. pm.test('Status and time', () => {
pm.expect(pm.response.json().status).to.equal('success');
pm.expect(pm.response.responseTime).to.be.below(500);
});

B. pm.test('Status and time', () => {
pm.expect(pm.response.json().status).to.equal('success');
pm.expect(pm.response.time).to.be.below(500);
});

C. pm.test('Status and time', () => {
pm.expect(pm.response.status).to.equal('success');
pm.expect(pm.response.time).to.be.lessThan(500);
});

D. pm.test('Status and time', () => {
pm.expect(pm.response.status).to.equal('success');
pm.expect(pm.response.responseTime).to.be.lessThan(500);
});

Solution

1. Step 1: Check how to access JSON fields and response time

   pm.response.json().status accesses the JSON 'status' field correctly. pm.response.responseTime gives response time in ms.

2. Step 2: Verify assertion methods

   to.equal('success') checks the status value. to.be.below(500) correctly asserts response time less than 500ms.

3. Step 3: Identify incorrect options

   pm.test('Status and time', () => { pm.expect(pm.response.json().status).to.equal('success'); pm.expect(pm.response.time).to.be.below(500); }); uses invalid pm.response.time. Options C and D use pm.response.status which is not the JSON field.

4. Final Answer:

   pm.test('Status and time', () => { pm.expect(pm.response.json().status).to.equal('success'); pm.expect(pm.response.responseTime).to.be.below(500); }); -> Option A

5. Quick Check:

   Use pm.response.json() and pm.response.responseTime for validation [OK]

Hint: Use pm.response.json() for data, pm.response.responseTime for timing [OK]

Common Mistakes:

• Using pm.response.status instead of JSON field
• Using wrong property for response time
• Mixing to.be.below and to.be.lessThan incorrectly