Generating dynamic data in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Postman pre-request script?

Consider this Postman pre-request script that generates a random integer between 1 and 10 and sets it as an environment variable. What will be the value type of the environment variable randomNumber after running this script?

Postman

const randomNumber = Math.floor(Math.random() * 10) + 1;
pm.environment.set('randomNumber', randomNumber);

A A number type, e.g., 7

B A string representing the number, e.g., "7"

C An object containing the number, e.g., {value: 7}

D Undefined, because environment variables cannot be set dynamically

💡 Hint

Remember that Postman environment variables store values as strings.

Postman environment variables always store values as strings, even if you set a number. So randomNumber will be a string like "7".

❓ assertion

intermediate

Which assertion correctly verifies a dynamic timestamp in Postman test script?

You have a response JSON with a field timestamp that contains the current time in ISO format. Which Postman test assertion correctly checks that timestamp is a valid ISO date string?

Postman

const jsonData = pm.response.json();

A pm.expect(Date.parse(jsonData.timestamp)).to.be.NaN;

B pm.expect(jsonData.timestamp).to.be.a('date');

C pm.expect(new Date(jsonData.timestamp).toString()).to.not.equal('Invalid Date');

D pm.expect(jsonData.timestamp).to.equal(new Date().toISOString());

💡 Hint

Check how JavaScript Date parsing works and how to detect invalid dates.

Option C parses the timestamp string into a Date object and checks that it is not 'Invalid Date', which means the timestamp is a valid ISO date string.

Option C is invalid because Postman assertions do not recognize 'date' as a type.

Option C incorrectly expects the parse to be NaN, which means invalid date.

Option C wrongly expects the timestamp to exactly match the current time, which is unlikely.

🔧 Debug

advanced

Why does this Postman script fail to generate a unique email each time?

This pre-request script is intended to generate a unique email by appending a timestamp, but it always sets the same email value. What is the cause?

Postman

const timestamp = pm.environment.get('timestamp');
if (!timestamp) {
  pm.environment.set('timestamp', Date.now());
}
const email = `user_${timestamp}@example.com`;
pm.environment.set('email', email);

A The timestamp is set only once and never updated, so email stays the same.

B Date.now() returns a constant value in Postman scripts.

C Environment variables cannot be used in pre-request scripts.

D The email variable is not set correctly due to string interpolation error.

💡 Hint

Check when and how the timestamp environment variable is updated.

The script sets the timestamp environment variable only if it does not exist. After the first run, the timestamp stays fixed, so the email does not change.

To fix, update the timestamp every time or use a local variable.

❓ framework

advanced

Which Postman feature best supports generating dynamic test data for multiple iterations?

You want to run a collection multiple times with different dynamic data generated on each iteration. Which Postman feature allows you to do this most effectively?

A Using the Collection Runner with a data file containing static values

B Manually changing environment variables before each run

C Using Postman monitors to schedule runs without data variation

D Using pre-request scripts with dynamic data generation and Collection Runner iterations

💡 Hint

Think about how to generate fresh data automatically for each iteration.

Option D allows dynamic data generation in pre-request scripts for each iteration in the Collection Runner, enabling unique data per run.

Option D uses static data, so no dynamic generation.

Option D is manual and not scalable.

Option D schedules runs but does not handle dynamic data per iteration.

🧠 Conceptual

expert

What is the main advantage of using dynamic data generation in API testing with Postman?

Why is generating dynamic data during API tests important instead of using only static test data?

A It helps simulate real-world scenarios by avoiding data duplication and conflicts.

B It reduces the need for assertions in test scripts.

C It guarantees that tests will always pass regardless of API changes.

D It eliminates the need for environment variables.

💡 Hint

Think about how static data can cause problems in repeated tests.

Dynamic data generation helps create unique inputs each time, preventing conflicts like duplicate user creation and better simulating real usage.

It does not reduce assertions or guarantee passing tests, nor does it remove the need for environment variables.