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.

Practice

1. What is the main purpose of using test utilities and helpers in Postman tests?

easy

A. To increase the number of test cases automatically

B. To make API requests faster

C. To simplify writing and maintaining tests by reusing code

D. To change the API endpoint dynamically

Solution

1. Step 1: Understand the role of helpers

   Helpers are small reusable functions that simplify test code and avoid repetition.

2. Step 2: Identify the main benefit

   They make tests easier to write and maintain by reusing common logic.

3. Final Answer:

   To simplify writing and maintaining tests by reusing code -> Option C

4. Quick Check:

   Helpers simplify tests = A [OK]

Hint: Helpers reduce repeated code in tests [OK]

Common Mistakes:

• Thinking helpers speed up API requests
• Believing helpers create more test cases automatically
• Confusing helpers with dynamic endpoint changes

2. Which of the following is the correct way to define a helper function in Postman test scripts?

easy

A. checkStatus(response) => response.status == 200

B. def checkStatus(response): return response.code == 200

C. var checkStatus = response => { response.code = 200 }

D. function checkStatus(response) { return response.code === 200; }

Solution

1. Step 1: Identify JavaScript syntax in Postman

   Postman test scripts use JavaScript, so function keyword is correct.

2. Step 2: Check function correctness

   function checkStatus(response) { return response.code === 200; } defines a function that returns true if response.code equals 200, which is valid.

3. Final Answer:

   function checkStatus(response) { return response.code === 200; } -> Option D

4. Quick Check:

   JavaScript function syntax = C [OK]

Hint: Use JavaScript function keyword for helpers [OK]

Common Mistakes:

• Using Python syntax in Postman scripts
• Using arrow function but with assignment errors
• Using single equals instead of triple equals

3. Given the helper function below, what will be the output of pm.test('Check status', () => { pm.expect(isSuccess({code: 200})).to.be.true; });?

function isSuccess(response) {
  return response.code === 200;
}

medium

A. Test passes because response code is 200

B. Test fails because response code is not 200

C. Syntax error in helper function

D. Runtime error due to undefined response

Solution

1. Step 1: Analyze helper function behavior

   The function returns true if response.code equals 200, which it does here.

2. Step 2: Evaluate test assertion

   The test expects isSuccess to be true, so the assertion passes.

3. Final Answer:

   Test passes because response code is 200 -> Option A

4. Quick Check:

   response.code === 200 -> true -> test passes [OK]

Hint: Check helper return value matches assertion [OK]

Common Mistakes:

• Assuming test fails without checking code value
• Confusing syntax error with correct JavaScript
• Thinking response is undefined when it is provided

4. You wrote this helper function in Postman tests but it throws an error:

function isValid(response) {
  return response.status = 200;
}

What is the error and how to fix it?

medium

A. Use '===' instead of '=' for comparison in return statement

B. Change function to arrow syntax

C. Remove the return keyword

D. Rename function to start with uppercase letter

Solution

1. Step 1: Identify assignment vs comparison

   The code uses '=' which assigns value instead of comparing.

2. Step 2: Correct the operator

   Replace '=' with '===' to compare response.status to 200.

3. Final Answer:

   Use '===' instead of '=' for comparison in return statement -> Option A

4. Quick Check:

   Comparison needs '===' not '=' [OK]

Hint: Use triple equals for comparisons in helpers [OK]

Common Mistakes:

• Confusing assignment '=' with comparison '==='
• Thinking arrow function fixes this error
• Removing return breaks function output

5. You want to create a helper that checks if a JSON response has a non-empty data array. Which helper function below correctly implements this check?

hard

A. function hasData(response) { return response.data == undefined; }

B. function hasData(response) { return Array.isArray(response.data) && response.data.length > 0; }

C. function hasData(response) { return response.data !== null; }

D. function hasData(response) { return response.data.length >= 0; }

Solution

1. Step 1: Check if response.data is an array

   Use Array.isArray to confirm data is an array.

2. Step 2: Verify array is not empty

   Check that length is greater than zero to ensure non-empty.

3. Final Answer:

   function hasData(response) { return Array.isArray(response.data) && response.data.length > 0; } -> Option B

4. Quick Check:

   Array check + length > 0 = D [OK]

Hint: Check array type and length > 0 for non-empty data [OK]

Common Mistakes:

• Only checking length without confirming array type
• Checking for null but ignoring empty arrays
• Using == undefined which is incorrect here