Output block 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 checks the response status and sets a variable. What will be the value of the variable isSuccess after running this test if the response status is 200?

Postman

pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
    pm.variables.set("isSuccess", true);
});

A The variable isSuccess is set to false

B The variable isSuccess is set to true

C The variable isSuccess is not set

D The test script throws an error

💡 Hint

Think about what happens when the status code matches 200 in the test.

The test checks if the response status is 200. If true, it sets the variable isSuccess to true. Since the response status is 200, the variable is set.

❓ assertion

intermediate

Which assertion correctly verifies the JSON response contains a key 'userId' with value 5?

You want to assert that the JSON response body has a key 'userId' equal to 5. Which Postman test assertion is correct?

Postman

const jsonData = pm.response.json();

A pm.expect(jsonData.userId).to.eql(5);

B pm.expect(jsonData['userId']).to.be.undefined;

C pm.expect(jsonData.userId).to.be.above(5);

D pm.expect(jsonData.userId).to.not.eql(5);

💡 Hint

Look for the assertion that checks equality to 5.

Option A correctly asserts that jsonData.userId equals 5. Other options check for undefined, greater than 5, or not equal to 5, which are incorrect.

🔧 Debug

advanced

Why does this Postman test script fail with a ReferenceError?

Examine the test script below. Why does it throw a ReferenceError when run?

Postman

pm.test("Check user name", function () {
    pm.expect(user.name).to.eql("Alice");
});

A The response does not contain a 'name' key

B The pm.expect syntax is incorrect

C The test function is missing a closing bracket

D The variable 'user' is not defined before use

💡 Hint

Check if the variable 'user' is declared or assigned.

The script uses 'user' without defining it. This causes a ReferenceError. The correct approach is to parse the response JSON first.

❓ framework

advanced

Which Postman test script correctly waits for an asynchronous fetch before asserting?

You want to fetch additional data asynchronously inside a test and then assert a value. Which script correctly handles the async operation?

A

pm.test("Async test", function () {
    fetch('https://api.example.com/data').then(res => res.json()).then(data => {
        pm.expect(data.status).to.eql('ok');
    });
});

B

pm.test("Async test", function () {
    const res = fetch('https://api.example.com/data');
    const data = res.json();
    pm.expect(data.status).to.eql('ok');
});

C

pm.test("Async test", async function () {
    const res = await fetch('https://api.example.com/data');
    const data = await res.json();
    pm.expect(data.status).to.eql('ok');
});

D

pm.test("Async test", function () {
    const data = fetch('https://api.example.com/data').json();
    pm.expect(data.status).to.eql('ok');
});

💡 Hint

Remember that async functions need to be awaited or handled with promises properly.

Option C uses async/await correctly inside the test function. Option C does not wait for the promise to resolve before ending the test. Options C and D misuse fetch and json() without awaiting promises.

🧠 Conceptual

expert

What is the main purpose of the Postman 'Tests' output block?

In Postman, the 'Tests' output block shows results after running a request. What is its main purpose?

A To display the results of test scripts including pass/fail status and assertion messages

B To edit the request body before sending

C To show the raw HTTP request headers sent to the server

D To configure environment variables for the request

💡 Hint

Think about what you see after tests run in Postman.

The 'Tests' output block shows which tests passed or failed and any messages from assertions. It does not show request headers, edit bodies, or configure variables.