Test utilities and helpers in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Postman test script?

Consider this Postman test script that uses a helper function to check response status. What will be the test result after running this script if the response status is 404?

Postman

function checkStatus(expected) {
  pm.test(`Status is ${expected}`, function () {
    pm.response.to.have.status(expected);
  });
}

checkStatus(200);

A Test passes because the function ignores the actual status

B Test fails with message 'Status is 200' because actual status is 404

C Test fails with a syntax error in the function

D Test passes because 404 is treated as 200 internally

💡 Hint

Think about what pm.response.to.have.status(expected) does when the actual status differs from expected.

The helper function checkStatus creates a test that expects the response status to be exactly the expected value. Since the response status is 404 but the function checks for 200, the test will fail with the message 'Status is 200'.

❓ assertion

intermediate

Which assertion correctly verifies a JSON response property using a helper?

You have a helper function that asserts a JSON property value in Postman tests. Which option correctly asserts that the response JSON has a property 'success' equal to true?

Postman

function assertPropertyEquals(property, expectedValue) {
  pm.test(`Property ${property} equals ${expectedValue}`, function () {
    pm.expect(pm.response.json()[property]).to.eql(expectedValue);
  });
}

A assertPropertyEquals('success', 1);

B assertPropertyEquals(success, 'true');

C assertPropertyEquals('success', 'true');

D assertPropertyEquals('success', true);

💡 Hint

Remember the difference between boolean true and string 'true' in JSON and JavaScript.

Option D correctly passes the property name as a string and the expected boolean value true. Options B and C use incorrect types or missing quotes, and D uses a number instead of boolean.

🔧 Debug

advanced

Why does this Postman test helper cause a runtime error?

This helper function is intended to check if a response header exists. Why does it cause a runtime error when used in a test?

Postman

function checkHeaderExists(headerName) {
  pm.test(`Header ${headerName} exists`, function () {
    pm.expect(pm.response.headers.get(headerName).length).to.be.above(0);
  });
}

checkHeaderExists('Content-Type');

A pm.response.headers.get(headerName) returns undefined if header missing, causing .length to fail

B pm.expect is not defined in Postman test scripts

C pm.response.headers.get requires a second argument for case sensitivity

D pm.test cannot be called inside a function

💡 Hint

What happens if the header is not present? What does .get() return?

If the header is missing, pm.response.headers.get(headerName) returns undefined. Calling .length on undefined causes a runtime error.

🧠 Conceptual

advanced

What is the main benefit of using test utility functions in Postman?

Why should you create and use test utility functions or helpers in your Postman test scripts?

A To avoid writing any assertions manually

B To make tests run faster by skipping assertions

C To reduce code duplication and improve test maintainability

D To automatically generate test reports without configuration

💡 Hint

Think about how helpers affect code reuse and clarity.

Test utility functions help reduce repeated code and make tests easier to update and maintain. They do not skip assertions or generate reports automatically.

❓ framework

expert

How to implement a reusable Postman test helper for validating JSON schema?

You want to create a reusable helper function in Postman to validate the response JSON against a given JSON schema. Which code snippet correctly implements this using the Ajv library available in Postman sandbox?

Postman

const Ajv = require('ajv');
const ajv = new Ajv();

function validateSchema(schema) {
  pm.test('Response matches JSON schema', function () {
    const validate = ajv.compile(schema);
    const valid = validate(pm.response.json());
    pm.expect(valid, JSON.stringify(validate.errors)).to.be.true;
  });
}

A Use ajv.compile(schema) once inside the test and validate pm.response.json() with pm.expect(valid).to.be.true

B Call ajv.validate(schema, pm.response.json()) inside pm.test and assert the result with pm.expect

C Use pm.response.to.have.jsonSchema(schema) directly without Ajv

D Use JSON.parse(pm.response.text()) and compare keys manually without Ajv

💡 Hint

Ajv requires compiling the schema before validation. Check how to assert validation results.

Option A correctly matches the provided code, which compiles the schema with ajv.compile(schema), validates the response JSON, and asserts the result. Option A describes using ajv.validate(schema, pm.response.json()), which is also valid but different from the code. Option A uses Postman's built-in pm.response.to.have.jsonSchema(schema) without explicit Ajv. Option A is manual and error-prone.