Why automated assertions validate responses in Postman - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Automated Assertions in API Testing

Why do automated assertions play a crucial role in validating API responses in Postman?

A They automatically check if the response data matches expected results without manual review.

B They replace the need for writing test scripts entirely.

C They slow down the testing process by adding unnecessary checks.

D They only verify the response time, ignoring data correctness.

💡 Hint

Think about how automation helps reduce human error and speeds up validation.

Automated assertions verify that the API response data matches what is expected, ensuring correctness quickly and reliably without manual checking.

❓ Predict Output

intermediate

Output of Postman Assertion Script

What will be the result of running this Postman test script if the API response status is 200?

Postman

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

A Test throws an error due to missing response body.

B Test passes regardless of the status code.

C Test passes because the status code matches 200.

D Test fails because the script syntax is incorrect.

💡 Hint

Check if the assertion matches the actual response status code.

The script asserts that the response status code must be 200. If it is, the test passes.

❓ assertion

advanced

Correct Assertion for JSON Response Property

Which assertion correctly verifies that the JSON response has a property success set to true?

Postman

pm.test('Response has success true', function () {
    // Assertion goes here
});

A pm.expect(pm.response.json().success).to.be.false;

B pm.expect(pm.response.json().success).to.eql(true);

C pm.expect(pm.response.text()).to.include('success:true');

D pm.expect(pm.response.json().success).to.equal('true');

💡 Hint

Check the data type and exact value of the success property.

Option B correctly checks that the success property is boolean true. Option B wrongly compares to string 'true'.

🔧 Debug

advanced

Identify the Assertion Error in Postman Test

Why does this Postman test fail even though the API returns status 200?

Postman

pm.test('Check status and message', function () {
    pm.response.to.have.status(200);
    pm.expect(pm.response.json().message).to.equal('Success');
});

A The response body is empty, so JSON parsing fails.

B The status code assertion is incorrect and causes failure.

C The test script syntax is invalid and throws an error.

D The response JSON <code>message</code> property is actually 'success' (lowercase), causing assertion failure.

💡 Hint

Check the exact spelling and case of the message property value.

The test fails because the expected string 'Success' does not match the actual 'success' in the response, causing the assertion to fail.

❓ framework

expert

Best Practice for Automated Assertions in Postman Collections

Which practice ensures reliable automated assertions across multiple API requests in a Postman collection?

A Use environment variables to store expected values and reference them in assertions for consistency.

B Hardcode expected values in each test script to avoid confusion.

C Skip assertions in pre-request scripts to speed up execution.

D Write assertions only for the first request and assume others behave similarly.

💡 Hint

Think about how to maintain consistency and reusability in tests.

Using environment variables for expected values allows easy updates and consistent assertions across requests, improving maintainability.

Practice

1. Why do automated assertions help when testing API responses in Postman?

easy

A. They delete incorrect responses from the server.

B. They make the API run faster.

C. They change the API response to fix errors.

D. They automatically check if the response matches expected results without manual review.

Solution

1. Step 1: Understand the role of automated assertions

   Automated assertions are used to verify if the API response data is correct without needing a person to check it manually.

2. Step 2: Identify what automated assertions do in Postman

   They run tests automatically after a request and confirm if the response meets the expected conditions.

3. Final Answer:

   They automatically check if the response matches expected results without manual review. -> Option D

4. Quick Check:

   Automated assertions = automatic response checks [OK]

Hint: Automated assertions save manual checking time [OK]

Common Mistakes:

• Thinking assertions speed up the API itself
• Believing assertions fix errors automatically
• Confusing assertions with deleting data

2. Which of the following is the correct syntax to assert that the response status code is 200 in Postman test script?

easy

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

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

C. pm.response.assertStatus(200);

D. pm.check('Status code', pm.response.status == 200);

Solution

1. Step 1: Recall Postman test syntax

   Postman uses pm.test() with a callback function to run assertions.

2. Step 2: Identify the correct assertion method

   The correct way to check status code is pm.response.to.have.status(200) inside the callback.

3. Final Answer:

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

4. Quick Check:

   pm.test + arrow function + .to.have.status(200) [OK]

Hint: Use pm.test with arrow function and .to.have.status() [OK]

Common Mistakes:

• Omitting the arrow function in pm.test
• Using incorrect assertion methods like assertStatus
• Passing boolean directly instead of function

3. Given this Postman test code:

pm.test('Check user name', () => {
  const jsonData = pm.response.json();
  pm.expect(jsonData.name).to.eql('Alice');
});

What will happen if the API response is {"name": "Bob"}?

medium

A. The test will pass because the name field exists.

B. The test will throw a syntax error.

C. The test will fail because the name is not 'Alice'.

D. The test will be skipped automatically.

Solution

1. Step 1: Understand the assertion in the test

   The test expects the JSON response's 'name' field to equal 'Alice'.

2. Step 2: Compare expected and actual response

   The actual response has 'name' as 'Bob', which does not match 'Alice', so the assertion fails.

3. Final Answer:

   The test will fail because the name is not 'Alice'. -> Option C

4. Quick Check:

   Expected 'Alice' but got 'Bob' = fail [OK]

Hint: Check if expected value matches actual response exactly [OK]

Common Mistakes:

• Assuming test passes if field exists regardless of value
• Thinking syntax error occurs for value mismatch
• Believing tests skip on assertion failure

4. You wrote this Postman test:

pm.test('Response has userId', () => {
  pm.expect(pm.response.json().userId).to.exist;
});

But the test always fails even when the response contains {"userId": 123}. What is the likely problem?

medium

A. The response might be a string, not JSON, causing json() to fail.

B. pm.response.json() is not called correctly inside the test.

C. The assertion should use .to.be.exist instead of .to.exist.

D. The test is missing a semicolon at the end.

Solution

1. Step 1: Check how pm.response.json() works

   pm.response.json() parses the response body as JSON. If the response is not valid JSON, it will throw an error or return undefined.

2. Step 2: Consider response format causing test failure

   If the response is a plain string or invalid JSON, json() fails, so userId is undefined and assertion fails.

3. Final Answer:

   The response might be a string, not JSON, causing json() to fail. -> Option A

4. Quick Check:

   Invalid JSON response breaks json() = test fail [OK]

Hint: Ensure response is valid JSON before using json() [OK]

Common Mistakes:

• Thinking missing semicolon causes test failure
• Using wrong assertion syntax like .to.be.exist
• Assuming json() always succeeds regardless of response

5. You want to write an automated assertion in Postman that checks if the response JSON array has at least one object with status equal to "active". Which test code correctly validates this?

hard

A. pm.test('Has active status', () => {
const data = pm.response.json();
pm.expect(data.some(item => item.status === 'active')).to.be.true;
});

B. pm.test('Has active status', () => {
const data = pm.response.json();
pm.expect(data.filter(item => item.status === 'active')).to.exist;
});

C. pm.test('Has active status', () => {
const data = pm.response.json();
pm.expect(data.find(item => item.status = 'active')).to.be.true;
});

D. pm.test('Has active status', () => {
const data = pm.response.json();
pm.expect(data.includes('active')).to.be.true;
});

Solution

1. Step 1: Understand the goal of the assertion

   The test must confirm at least one object in the array has status exactly 'active'.

2. Step 2: Analyze each option's correctness

   pm.test('Has active status', () => { const data = pm.response.json(); pm.expect(data.some(item => item.status === 'active')).to.be.true; }); uses data.some() which returns true if any item matches the condition, then asserts true correctly.
   pm.test('Has active status', () => { const data = pm.response.json(); pm.expect(data.filter(item => item.status === 'active')).to.exist; }); uses filter() but checks .to.exist which is always true for an array, not a boolean.
   pm.test('Has active status', () => { const data = pm.response.json(); pm.expect(data.find(item => item.status = 'active')).to.be.true; }); uses assignment (=) instead of comparison (===), causing a bug.
   pm.test('Has active status', () => { const data = pm.response.json(); pm.expect(data.includes('active')).to.be.true; }); uses includes('active') which checks for string presence, not object property.

3. Final Answer:

   pm.test('Has active status', () => { const data = pm.response.json(); pm.expect(data.some(item => item.status === 'active')).to.be.true; }); -> Option A

4. Quick Check:

   Use some() + strict equality + expect true [OK]

Hint: Use some() to check condition on array items [OK]

Common Mistakes:

• Using assignment (=) instead of comparison (===)
• Checking filter() result existence instead of boolean
• Using includes() on array of objects incorrectly