Default and conditional responses in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the test result of this Postman test script?

Given the following Postman test script, what will be the test result if the response status code is 404?

Postman

pm.test('Status code is 200 or 201', function () {
    pm.expect(pm.response.code).to.be.oneOf([200, 201]);
});

A Test fails because 404 is not in [200, 201]

B Test passes because 404 is considered a success

C Test throws an error due to invalid syntax

D Test is skipped automatically

💡 Hint

Check which status codes are accepted by the oneOf assertion.

The test expects the response code to be either 200 or 201. Since 404 is not in this list, the assertion fails and the test fails.

❓ assertion

intermediate

Which assertion correctly checks for a default JSON property in Postman?

You want to verify that the JSON response always contains a property named 'success' with a boolean value. Which assertion is correct?

A pm.expect(pm.response.json().success).to.be.a('boolean');

B pm.expect(pm.response.json().success).to.be.true || false;

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

D pm.expect(pm.response.json().success).to.be('boolean');

💡 Hint

Check the syntax for type checking in Postman assertions.

Option A correctly checks that the 'success' property is of boolean type. Option A wrongly compares to string 'true'. Option A is invalid syntax. Option A uses incorrect assertion syntax.

🧠 Conceptual

advanced

What happens if no conditional test matches in a Postman test script?

In a Postman test script, you have multiple conditional tests checking response codes 200, 201, and 404. What is the default behavior if the response code is 500 and no condition matches?

A No test runs and the test suite passes by default

B All tests fail automatically because no condition matched

C Postman throws a runtime error due to unmatched conditions

D Tests not matching conditions are skipped, but overall test result depends on other tests

💡 Hint

Think about how Postman handles tests that are not explicitly triggered.

Tests that do not run due to conditions are skipped. The overall test result depends on the tests that do run. Postman does not fail or error automatically if no condition matches.

🔧 Debug

advanced

Why does this Postman test script always fail?

Analyze the following Postman test script and identify why it always fails regardless of response status code: pm.test('Check status', () => { if (pm.response.code === 200) { pm.expect(true).to.be.true; } else if (pm.response.code === 404) { pm.expect(true).to.be.true; } });

Postman

pm.test('Check status', () => {
  if (pm.response.code === 200) {
    pm.expect(true).to.be.true;
  } else if (pm.response.code === 404) {
    pm.expect(true).to.be.true;
  }
});

A The test always fails because pm.expect(true).to.be.true is incorrect

B The test syntax is invalid causing failure

C The test fails when response code is neither 200 nor 404 because no assertion runs

D The test fails because pm.response.code is undefined

💡 Hint

What happens if the response code is 500?

If the response code is not 200 or 404, no assertion runs inside the test callback. Postman treats this as a failed test because no assertion was made.

❓ framework

expert

How to implement a default response handler in Postman tests?

You want to write a Postman test script that handles multiple response codes (200, 201, 404) with specific assertions and also has a default assertion for any other response code. Which script correctly implements this?

A

pm.test('Response code check', () => {
  pm.expect(pm.response.code).to.be.oneOf([200,201,404]);
});

B

pm.test('Response code check', () => {
  switch(pm.response.code) {
    case 200:
      pm.expect(pm.response.code).to.equal(200);
      break;
    case 201:
      pm.expect(pm.response.code).to.equal(201);
      break;
    case 404:
      pm.expect(pm.response.code).to.equal(404);
      break;
    default:
      pm.expect.fail(`Unexpected status code: ${pm.response.code}`);
  }
});

C

pm.test('Response code check', () => {
  if ([200,201,404].includes(pm.response.code)) {
    pm.expect(pm.response.code).to.be.oneOf([200,201,404]);
  }
});

D

pm.test('Response code check', () => {
  if (pm.response.code === 200) {
    pm.expect(pm.response.code).to.equal(200);
  } else if (pm.response.code === 201) {
    pm.expect(pm.response.code).to.equal(201);
  } else if (pm.response.code === 404) {
    pm.expect(pm.response.code).to.equal(404);
  } else {
    pm.expect(pm.response.code).to.be.oneOf([200,201,404]);
  }
});

💡 Hint

Look for a default case that fails the test explicitly.

Option B uses a switch with a default case that explicitly fails the test if the response code is unexpected. Options B, C, and D do not fail the test for unexpected codes properly.