Why Header assertions in Postman? - Purpose & Use Cases

The Big Idea

What if you could instantly know if your API headers are wrong without looking at them yourself?

The Scenario

Imagine you are testing a website's API manually by checking each response header one by one in the browser or Postman interface.

You have to look at each header like Content-Type, Authorization, or Cache-Control and remember if they are correct for every request.

The Problem

This manual checking is slow and tiring because you must do it for many requests.

It is easy to miss a wrong header or forget to check some headers, causing bugs to slip through.

Also, repeating this for every test wastes a lot of time and energy.

The Solution

Header assertions let you write simple tests that automatically check if the response headers are exactly what you expect.

Postman runs these tests every time you send a request and tells you immediately if something is wrong.

This saves time, reduces mistakes, and makes your testing reliable and fast.

Before vs After

✗ Before

Look at response headers manually each time and note down if they look correct.

✓ After

pm.test('Content-Type is JSON', () => pm.response.to.have.header('Content-Type', 'application/json'));

What It Enables

It enables fast, automatic checks of response headers so you catch errors early and keep your API reliable.

Real Life Example

When building an app that talks to a server, you want to be sure the server sends the right Content-Type header so your app can understand the data.

Header assertions automatically verify this every time you test the API.

Key Takeaways

Manual header checks are slow and error-prone.

Header assertions automate and speed up this process.

They help catch mistakes early and keep APIs working correctly.

Practice

1. What does the Postman assertion pm.response.to.have.header('Content-Type') check for?

easy

A. It checks if the response body contains the text 'Content-Type'.

B. It checks if the response includes a header named 'Content-Type'.

C. It verifies the status code of the response is 200.

D. It checks if the request has a header named 'Content-Type'.

Solution

1. Step 1: Understand the assertion method

   The method pm.response.to.have.header() is used to check response headers.

2. Step 2: Identify what is being checked

   The argument 'Content-Type' specifies the header name to look for in the response.

3. Final Answer:

   It checks if the response includes a header named 'Content-Type'. -> Option B

4. Quick Check:

   Header presence check = It checks if the response includes a header named 'Content-Type'. [OK]

Hint: Look for 'response.to.have.header' to check response headers [OK]

Common Mistakes:

• Confusing response headers with response body content
• Checking request headers instead of response headers
• Assuming it checks status codes

2. Which of the following is the correct syntax to assert that the response header 'Cache-Control' has the value 'no-cache' in Postman?

easy

A. pm.expect(pm.response.headers.get('Cache-Control')).to.eql('no-cache');

B. pm.response.to.have.header('Cache-Control', 'no-cache');

C. pm.expect(response.headers['Cache-Control']).to.equal('no-cache');

D. pm.response.headers('Cache-Control').equals('no-cache');

Solution

1. Step 1: Recall correct Postman syntax for header value assertion

   Use pm.expect(pm.response.headers.get('Header-Name')).to.eql('value') to check header value.

2. Step 2: Check each option's syntax

   pm.expect(pm.response.headers.get('Cache-Control')).to.eql('no-cache'); uses correct method headers.get() and assertion to.eql(). Others have syntax errors or incorrect usage.

3. Final Answer:

   pm.expect(pm.response.headers.get('Cache-Control')).to.eql('no-cache'); -> Option A

4. Quick Check:

   Use headers.get() with pm.expect() [OK]

Hint: Use headers.get('name') inside pm.expect() for header value checks [OK]

Common Mistakes:

• Using incorrect method like headers('name')
• Trying to pass two arguments to to.have.header()
• Using response.headers as an object without get()

3. Given this Postman test snippet:

pm.test('Check Server header', () => {
  pm.expect(pm.response.headers.get('Server')).to.equal('nginx');
});

What will happen if the response header 'Server' is 'Apache'?

medium

A. The test will be skipped automatically.

B. The test will pass because the header exists.

C. The test will throw a syntax error.

D. The test will fail because the header value is not 'nginx'.

Solution

1. Step 1: Understand the assertion

   The test expects the 'Server' header value to be exactly 'nginx'.

2. Step 2: Compare actual header value

   The actual header value is 'Apache', which does not match 'nginx', so assertion fails.

3. Final Answer:

   The test will fail because the header value is not 'nginx'. -> Option D

4. Quick Check:

   Value mismatch causes failure [OK]

Hint: Exact value mismatch causes test failure [OK]

Common Mistakes:

• Assuming header presence is enough to pass
• Thinking syntax error occurs on value mismatch
• Believing test skips on assertion failure

4. You wrote this Postman test:

pm.test('Check Content-Length', () => {
  pm.expect(pm.response.headers.get('Content-Length')).to.be('1234');
});

Why does this test fail to run correctly?

medium

A. Because the value '1234' is a number and should not be in quotes.

B. Because 'Content-Length' header does not exist in the response.

C. Because to.be is not a valid assertion method; it should be to.equal or to.eql.

D. Because pm.response.headers.get returns an array, not a string.

Solution

1. Step 1: Check assertion method correctness

   The method to.be is not a valid Chai assertion method for value equality in Postman.

2. Step 2: Identify correct assertion method

   Use to.equal or to.eql to compare values correctly.

3. Final Answer:

   Because to.be is not a valid assertion method; it should be to.equal or to.eql. -> Option C

4. Quick Check:

   Use to.equal() for value assertions [OK]

Hint: Use to.equal() or to.eql() for value checks, not to.be [OK]

Common Mistakes:

• Using to.be() instead of to.equal()
• Assuming header value is numeric without quotes
• Thinking headers.get() returns array

5. You want to write a Postman test to verify that the response has a header named 'X-Rate-Limit' and its value is a number greater than 1000. Which code snippet correctly achieves this?

hard

A. pm.test('X-Rate-Limit check', () => {
const val = Number(pm.response.headers.get('X-Rate-Limit'));
pm.expect(val).to.be.above(1000);
});

B. pm.test('X-Rate-Limit check', () => {
pm.expect(pm.response.headers.get('X-Rate-Limit')).to.be.greaterThan(1000);
});

C. pm.test('X-Rate-Limit check', () => {
pm.expect(pm.response.headers.has('X-Rate-Limit')).to.equal(true);
pm.expect(pm.response.headers.get('X-Rate-Limit') > 1000).to.be.true;
});

D. pm.test('X-Rate-Limit check', () => {
pm.expect(parseInt(pm.response.headers.get('X-Rate-Limit'))).to.be.greaterThan(1000);
});

Solution

1. Step 1: Extract and convert header value to number

   Use Number() to convert the header string value to a number for comparison.

2. Step 2: Use correct assertion for numeric comparison

   Use pm.expect(val).to.be.above(1000) to check if the number is greater than 1000.

3. Final Answer:

   pm.test('X-Rate-Limit check', () => { const val = Number(pm.response.headers.get('X-Rate-Limit')); pm.expect(val).to.be.above(1000); }); -> Option A

4. Quick Check:

   Convert header to number, then assert with to.be.above() [OK]

Hint: Convert header string to number before numeric assertions [OK]

Common Mistakes:

• Using to.be.greaterThan() which is not a valid Chai method
• Not converting header value to number before comparison
• Trying to compare header string directly to number