Why response validation confirms correctness in Postman - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the response status is 200.

Postman

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

Drag options to blanks, or click blank then click option'

A404

B200

C500

D201

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong status codes like 404 or 500.

The status code 200 means the request was successful. Checking this confirms the response is correct.

2fill in blank

medium

Complete the code to check if the response body contains the key 'success'.

Postman

pm.test('Response has success key', function () { pm.expect(pm.response.json()).to.have.property([1]); });

Drag options to blanks, or click blank then click option'

A'status'

B'error'

C'success'

D'message'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong key names like 'error' or 'message'.

Checking for the 'success' key confirms the response includes expected data.

3fill in blank

hard

Fix the error in the assertion to check if the response time is less than 200ms.

Postman

pm.test('Response time is fast', function () { pm.expect(pm.response.responseTime).to.be.[1](200); });

Drag options to blanks, or click blank then click option'

Abelow

Babove

ClessThan

DgreaterThan

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'lessThan' which is not a valid Chai method.

The correct assertion method is 'below' to check response time is under 200ms.

4fill in blank

hard

Fill both blanks to check if the response JSON has a 'status' key equal to 'success'.

Postman

pm.test('Status is success', function () { pm.expect(pm.response.json()).to.have.[1]('status').that.[2]('success'); });

Drag options to blanks, or click blank then click option'

Aproperty

Bequal

Cequals

Dcontain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'contain' instead of 'equal' for exact match.

'property' checks the key exists, and 'equal' checks its value matches 'success'.

5fill in blank

hard

Fill all three blanks to validate the response JSON array length is greater than 0 and contains the key 'id'.

Postman

pm.test('Response array valid', function () { const data = pm.response.json(); pm.expect(data.length).to.be.[1](0); pm.expect(data[0]).to.have.[2]([3]); });

Drag options to blanks, or click blank then click option'

Aabove

Bproperty

C'id'

Dbelow

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'below' instead of 'above' for length check.

'above' checks length > 0, 'property' checks key exists, and 'id' is the key name.

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