API versioning validation in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the test result of this Postman script validating API version header?

Given this Postman test script that checks the API version in response headers, what will be the test result?

Postman

pm.test('API version is 2.0', () => {
    pm.response.to.have.header('X-API-Version');
    pm.expect(pm.response.headers.get('X-API-Version')).to.eql('2.0');
});

A Test passes if header 'X-API-Version' exists, ignoring its value

B Test always passes regardless of header value

C Test fails with syntax error due to missing semicolon

D Test passes if header 'X-API-Version' equals '2.0', otherwise fails

💡 Hint

Check how the test asserts the header value exactly equals '2.0'.

The test first checks the header exists, then asserts its value equals '2.0'. If the header is missing or value differs, the test fails.

❓ assertion

intermediate

Which assertion correctly verifies API version in JSON response body?

You receive this JSON response: {"version": "v1.3"}. Which Postman assertion correctly checks the version is 'v1.3'?

A pm.expect(pm.response.json().version).to.have.property('v1.3');

B pm.expect(pm.response.json().version).to.equal('v1.3');

C pm.expect(pm.response.json().version).to.be('v1.3');

D pm.expect(pm.response.json().version).to.eql(1.3);

💡 Hint

Remember the version is a string, so the assertion must compare string values.

Option B correctly compares the string value 'v1.3'. Option B compares to a number, which is wrong. Option B uses invalid syntax. Option B wrongly treats the version as an object.

🔧 Debug

advanced

Why does this Postman test fail when validating API version in URL path?

Test code:

pm.test('API version in URL is v2', () => {
    const url = pm.request.url.toString();
    pm.expect(url.includes('/v2/')).to.be.true;
});

But the test fails even though the URL is https://api.example.com/v2users. Why?

A The test fails because the URL string does not contain '/v2/' exactly due to missing trailing slash

B The test fails because pm.request.url.toString() returns an object, not a string

C The test fails because pm.expect syntax is incorrect; should use to.equal(true)

D The test fails because includes() is case-sensitive and URL has uppercase 'V2'

💡 Hint

Check the exact substring searched and the actual URL string.

The URL is 'https://api.example.com/v2users' which contains '/v2' but not '/v2/' exactly. The includes('/v2/') check fails because of the trailing slash in the search string.

❓ framework

advanced

Which Postman test script correctly validates API version in both header and JSON body?

Choose the script that checks the response header 'X-API-Version' equals '1.0' and the JSON body field 'apiVersion' equals '1.0' in one test.

A

pm.test('API version check', () => {
  pm.expect(pm.response.headers['X-API-Version']).to.equal('1.0');
  pm.expect(pm.response.json().apiVersion).to.eql('1.0');
});

B

pm.test('API version check', () => {
  pm.response.to.have.header('X-API-Version', '1.0');
  pm.expect(pm.response.json().apiVersion).to.equal(1.0);
});

C

pm.test('API version check', () => {
  pm.expect(pm.response.headers.get('X-API-Version')).to.eql('1.0');
  pm.expect(pm.response.json().apiVersion).to.eql('1.0');
});

D

pm.test('API version check', () => {
  pm.expect(pm.response.headers.get('X-API-Version')).to.equal(1.0);
  pm.expect(pm.response.json().apiVersion).to.eql('1.0');
});

💡 Hint

Check correct header access method and matching string types.

Option C uses pm.response.headers.get() correctly and compares strings with to.eql(). Option C uses invalid header assertion syntax and compares string to number. Option C incorrectly accesses headers as object. Option C compares string header to number 1.0.

🧠 Conceptual

expert

What is the best practice for API versioning validation in automated tests?

Which statement best describes a robust approach to validate API versioning in automated API tests?

A Validate API version in both response headers and response body to ensure consistency and detect mismatches

B Validate API version only in response headers to keep tests simple and avoid parsing response body

C Validate API version only in the URL path since headers and body can be unreliable

D Skip API version validation in tests because versioning is handled by API gateway and not relevant to functional tests

💡 Hint

Think about how to catch version mismatches effectively.

Validating both headers and body ensures the API version is consistent across all parts of the response. Relying on only one source risks missing discrepancies. Skipping validation or checking only URL is insufficient for robust testing.