Output block in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Output block in Postman tests?

An Output block in Postman is a section in the test script where you write code to check the response and print results or messages. It helps you see if your test passed or failed.

beginner

How do you write an assertion inside an Output block in Postman?

You use the pm.test() function with a description and a function that contains pm.expect() to check values. For example: pm.test('Status is 200', () => { pm.response.to.have.status(200); });

beginner

Why is it important to use clear messages in Output blocks?

Clear messages help you understand what each test checks and if it passed or failed. It’s like reading a clear label on a box to know what’s inside.

beginner

What does pm.response.to.have.status(200) check in an Output block?

It checks if the response from the server has a status code of 200, which means the request was successful.

beginner

How can you print custom messages in the Output block for debugging?

You can use console.log('Your message') inside the test script to print messages in Postman’s console for easier debugging.

What is the main purpose of the Output block in Postman tests?

A To write assertions and show test results

B To send HTTP requests

C To create new APIs

D To store environment variables

The Output block is where you write assertions to check responses and display test results.

Which function is used to define a test inside the Output block?

A pm.sendRequest()

B pm.test()

C pm.response()

D pm.expect()

pm.test() defines a test with a name and a function containing assertions.

What does pm.expect(pm.response.code).to.equal(200) check?

A Response time is 200ms

B Response body length is 200

C Response header count is 200

D Response status code is 200

It checks that the HTTP response status code equals 200, meaning success.

Where can you see messages printed by console.log() in Postman?

A In the Postman Console

B In the response body

C In the environment variables

D In the request URL

console.log() messages appear in the Postman Console for debugging.

Why should test messages be clear and descriptive?

A To confuse the tester

B To make tests run faster

C To easily understand test results

D To reduce the number of tests

Clear messages help testers quickly understand what each test checks and its result.

Explain what an Output block is in Postman and how it helps in testing.

Think about where you write checks and see if your API works as expected.

Describe how to write a simple test in the Output block to check if the response status is 200.

Start with pm.test and inside use pm.expect to check the status.

Practice

1. What does the Output block in Postman primarily display after running a request?

easy

A. The list of saved environments

B. The raw API request headers only

C. The Postman app settings and preferences

D. The results of test scripts and any console logs

Solution

1. Step 1: Understand the purpose of the Output block

   The Output block shows what happened after running a request, including test results and logs.

2. Step 2: Identify what is NOT shown in the Output block

   Settings, environments, or just headers are not shown here; only test results and logs appear.

3. Final Answer:

   The results of test scripts and any console logs -> Option D

4. Quick Check:

   Output block = test results + logs [OK]

Hint: Output block shows test results and logs only [OK]

Common Mistakes:

• Confusing Output block with environment settings
• Thinking it shows only request headers
• Assuming it displays saved collections

2. Which of the following is the correct way to log a message to the Output block in a Postman test script?

easy

A. log('Test passed')

B. print('Test passed')

C. console.log('Test passed')

D. echo('Test passed')

Solution

1. Step 1: Recall JavaScript logging syntax in Postman

   Postman test scripts use JavaScript, and console.log() is the standard way to log messages.

2. Step 2: Identify incorrect logging functions

   Functions like print(), log(), and echo() are not valid in Postman scripts.

3. Final Answer:

   console.log('Test passed') -> Option C

4. Quick Check:

   Use console.log() to log messages [OK]

Hint: Use console.log() to print messages in Output block [OK]

Common Mistakes:

• Using print() instead of console.log()
• Trying to use echo() which is not JavaScript
• Forgetting parentheses in console.log

3. Given this Postman test script:

pm.test('Status code is 200', () => {
    pm.response.to.have.status(200);
});
console.log('Test completed');

What will you see in the Output block after running the request if the response status is 200?

medium

A. Test failed and no message

B. Test passed and 'Test completed' message

C. Only 'Test completed' message

D. No output at all

Solution

1. Step 1: Analyze the test script behavior

   The test checks if the response status is 200. If true, the test passes.

2. Step 2: Understand console.log output

   The console.log prints 'Test completed' regardless of test result.

3. Final Answer:

   Test passed and 'Test completed' message -> Option B

4. Quick Check:

   Passing test + console.log message = Test passed and 'Test completed' message [OK]

Hint: Passing test shows pass + console.log output [OK]

Common Mistakes:

• Assuming console.log only shows on failure
• Thinking test fails if console.log runs
• Ignoring test result messages

4. You wrote this Postman test script:

pm.test('Response time is less than 200ms', () => {
    pm.expect(pm.response.responseTime).to.be.below(200);
});
console.log('Check complete');

But after running, the Output block shows no test results or logs. What is the most likely problem?

medium

A. The test script is not saved or attached to the request

B. The response time is exactly 200ms, so test is skipped

C. console.log is not supported in Postman

D. The Output block only shows errors, not passes

Solution

1. Step 1: Check why Output block is empty

   If no test results or logs appear, the script might not be running at all.

2. Step 2: Confirm script attachment and saving

   Scripts must be saved and attached to the request to run and show output.

3. Final Answer:

   The test script is not saved or attached to the request -> Option A

4. Quick Check:

   Unsaved script = no output [OK]

Hint: Always save and attach test scripts to see output [OK]

Common Mistakes:

• Thinking console.log is unsupported
• Assuming Output block hides passing tests
• Believing test skips on exact boundary values

5. You want to verify in Postman that a JSON response contains a key userId with value 5, and log 'User verified' only if the test passes. Which test script will correctly show this in the Output block?

hard

A. pm.test('UserId is 5', () => {
pm.expect(pm.response.json().userId).to.eql(5);
});
if(pm.response.json().userId === 5) console.log('User verified');

B. pm.test('UserId is 5', () => {
pm.expect(pm.response.json().userId).to.eql(5);
console.log('User verified');
});

C. if(pm.response.json().userId === 5) {
pm.test('UserId is 5', () => {});
console.log('User verified');
}

D. pm.test('UserId is 5', () => {
pm.expect(pm.response.json().userId).to.eql(5);
});
console.log('User verified');

Solution

1. Step 1: Understand conditional logging requirement

   pm.test callbacks always execute fully; assertions don't halt execution. Log only on pass requires a matching condition.

2. Step 2: Analyze options

   A: unconditional log after test - always logs.
   B: log inside pm.test - executes even if assertion fails.
   C: empty pm.test - no proper verification.
   D: proper assertion test + matching if condition - logs only if userId === 5 (test passes).

3. Final Answer:

   pm.test('UserId is 5', () => { pm.expect(pm.response.json().userId).to.eql(5); }); if(pm.response.json().userId === 5) console.log('User verified'); -> Option A

4. Quick Check:

   if() matching test condition = log only on pass [OK]

Hint: Use if() matching assertion after pm.test for log only on pass [OK]

Common Mistakes:

• Putting console.log inside pm.test (runs on fail too)
• Logging unconditionally outside pm.test
• Using empty pm.test callback