Status code assertion in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ assertion

intermediate

Check for successful status code 200

You want to write a Postman test to verify the response status code is exactly 200. Which code snippet correctly asserts this?

A pm.test('Status code is 200', () => { pm.response.statusCode(200); });

B pm.test('Status code is 200', () => { pm.response.to.be.status(200); });

C pm.test('Status code is 200', () => { pm.response.status === 200; });

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

💡 Hint

Use the Postman built-in assertion syntax for status codes.

Option D uses the correct Postman Chai assertion syntax to check the response status code equals 200. Other options either use incorrect properties or methods.

❓ assertion

intermediate

Assert status code is in 2xx range

Which Postman test code correctly asserts that the response status code is any 2xx success code?

A pm.test('Status code is 2xx', () => { pm.expect(pm.response.code).to.be.within(200, 299); });

B pm.test('Status code is 2xx', () => { pm.response.to.have.status(2xx); });

C pm.test('Status code is 2xx', () => { pm.expect(pm.response.status).to.be.above(199).and.below(300); });

D pm.test('Status code is 2xx', () => { pm.response.statusCode >= 200 && pm.response.statusCode < 300; });

💡 Hint

Use numeric range assertions with pm.expect.

Option A correctly uses pm.expect with .to.be.within(200, 299) to check the status code range. Option A lacks an assertion, B uses invalid syntax, and C uses pm.response.status which is a string, not a number.

❓ Predict Output

advanced

Identify the test result for status code assertion

Given this Postman test code and a response with status code 404, what will be the test result?

Postman

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

A Test fails because the response status is 404, not 200.

B Test passes because 404 is a valid HTTP status code.

C Test throws a runtime error due to invalid assertion syntax.

D Test is skipped because status code assertions only run on 2xx codes.

💡 Hint

The assertion expects exactly 200 but response is 404.

The test checks for status 200 but the response is 404, so the assertion fails and the test fails.

🔧 Debug

advanced

Find the error in this status code assertion

This Postman test code is intended to check for status 201 but it does not work as expected. What is the error?

Postman

pm.test('Status code is 201', () => { pm.response.to.have.status == 201; });

A The status code 201 is invalid for HTTP responses.

B Using '==' instead of calling the function causes no assertion to run.

C pm.response.to.have.status requires a string, not a number.

D The test should use pm.expect instead of pm.response.

💡 Hint

Check the syntax for calling assertion methods.

The code uses '==' which compares but does not call the assertion method. The assertion must be called as a function with parentheses.

🧠 Conceptual

expert

Understanding status code assertion behavior in Postman

Which statement best describes how Postman handles status code assertions in tests?

A Postman automatically retries requests if status code assertions fail.

B Status code assertions in Postman only check if the code is a string, not a number.

C Postman assertions for status codes use Chai.js syntax and fail the test if the assertion is false.

D Postman ignores status code assertions if the response body is empty.

💡 Hint

Think about how assertion libraries work in Postman tests.

Postman uses Chai.js assertion library. If a status code assertion fails, the test fails immediately. Postman does not retry or ignore assertions based on response body.