Dynamic assertion values in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ assertion

intermediate

Dynamic assertion with timestamp validation

You have a Postman test that checks if the response JSON contains a timestamp field that should be within the last 5 minutes. Which assertion correctly validates this dynamically?

Postman

const responseTime = new Date(pm.response.json().timestamp);
const now = new Date();
const diffMinutes = (now - responseTime) / 60000;

A pm.test('Timestamp is recent', () => { pm.expect(diffMinutes).to.be.at.least(5); });

B pm.test('Timestamp is recent', () => { pm.expect(diffMinutes).to.be.below(5); });

C pm.test('Timestamp is recent', () => { pm.expect(diffMinutes).to.equal(5); });

D pm.test('Timestamp is recent', () => { pm.expect(diffMinutes).to.be.above(5); });

💡 Hint

Think about how to check if the timestamp is within the last 5 minutes, not older.

Option B correctly asserts that the difference in minutes is less than 5, meaning the timestamp is recent. Other options check for wrong conditions.

❓ Predict Output

intermediate

Output of dynamic variable assertion in Postman

Given this Postman test code, what will be the test result if the response JSON is {"count": 10} and the environment variable 'expectedCount' is set to '10' (string)?

Postman

const actualCount = pm.response.json().count;
const expectedCount = pm.environment.get('expectedCount');
pm.test('Count matches expected', () => {
  pm.expect(actualCount).to.eql(Number(expectedCount));
});

A Test passes because pm.expect does type coercion automatically

B Test fails because actualCount is number but expectedCount is string

C Test fails with TypeError due to type mismatch

D Test passes because actualCount (10) equals Number(expectedCount) (10)

💡 Hint

Check how the expectedCount is converted before assertion.

The code converts expectedCount to a number before comparing, so both sides are numbers 10, making the test pass.

🔧 Debug

advanced

Debugging a failing dynamic assertion in Postman

This Postman test is supposed to check if the response header 'x-rate-limit-remaining' is greater than zero. However, it always fails. What is the cause?

Postman

const remaining = pm.response.headers.get('x-rate-limit-remaining');
pm.test('Rate limit remaining positive', () => {
  pm.expect(remaining).to.be.above(0);
});

A pm.expect cannot compare header values

B Header name is incorrect; should be 'X-Rate-Limit-Remaining' with capitals

C remaining is a string, so the numeric comparison fails; convert to number first

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

💡 Hint

Check the data type of the header value before comparing.

Headers are strings by default. Comparing string '10' with number 0 using .above fails. Converting to number fixes it.

❓ framework

advanced

Using dynamic variables in Postman pre-request scripts

You want to set a dynamic timestamp variable 'currentTime' in Postman before sending the request, so you can use it in assertions later. Which code correctly sets this environment variable?

A pm.environment.set('currentTime', new Date().toISOString());

B pm.environment.get('currentTime', new Date().toISOString());

C pm.variables.set('currentTime', new Date());

D pm.environment.set('currentTime', Date.now);

💡 Hint

Remember how to set environment variables and the correct way to get current time as string.

Option A correctly sets the environment variable to the current ISO timestamp string. Option A tries to get instead of set. Option A uses pm.variables which is temporary and stores Date object, not string. Option A sets a function reference, not the timestamp.

🧠 Conceptual

expert

Why use dynamic assertion values in API testing?

Which is the best reason to use dynamic assertion values in Postman tests instead of hardcoded values?

A To ensure tests adapt to changing data and remain valid over time

B To make tests run faster by avoiding fixed values

C To reduce the number of tests needed by using random values

D To avoid writing any assertions manually

💡 Hint

Think about test reliability when data changes.

Dynamic assertions allow tests to check values that change, like timestamps or IDs, keeping tests valid and meaningful.