Random data generation in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Postman script generating a random integer?

Consider this Postman pre-request script snippet that generates a random integer between 1 and 10 inclusive. What is the possible output stored in the variable randomInt?

Postman

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

A Any integer from 1 to 10 inclusive

B Any integer from 0 to 9 inclusive

C Any integer from 1 to 9 inclusive

D Any integer from 0 to 10 inclusive

💡 Hint

Remember how Math.random() and Math.floor() work together to generate integers in a range.

Math.random() generates a decimal from 0 (inclusive) up to but not including 1. Multiplying by 10 gives a number from 0 up to but not including 10. Math.floor() rounds down to the nearest integer, so possible values are 0 to 9. Adding 1 shifts the range to 1 to 10 inclusive.

❓ assertion

intermediate

Which assertion correctly verifies a random email format in Postman test script?

You want to check that a randomly generated email stored in pm.environment.get('randomEmail') matches the pattern [e-mail]. Which assertion is correct?

Postman

const email = pm.environment.get('randomEmail');

A pm.test('Email format is valid', () => { pm.expect(email).to.have.string(/^[\w.-]+@[\w.-]+\.com$/); });

B pm.test('Email format is valid', () => { pm.expect(email).to.equal(/^[\w.-]+@[\w.-]+\.com$/); });

C pm.test('Email format is valid', () => { pm.expect(email).to.include(/^[\w.-]+@[\w.-]+\.com$/); });

D pm.test('Email format is valid', () => { pm.expect(email).to.match(/^[\w.-]+@[\w.-]+\.com$/); });

💡 Hint

Check which assertion method tests a string against a regular expression.

The .to.match() method tests if the string matches the given regex pattern. Other methods like .equal(), .include(), and .have.string() do not accept regex as argument for matching.

🔧 Debug

advanced

Why does this Postman script fail to generate a random UUID correctly?

This script tries to generate a random UUID and set it as an environment variable. Why does it fail?

Postman

const uuid = '{{$guid}}';
pm.environment.set('randomUUID', uuid);
console.log(uuid);

A pm.environment.set() cannot store strings generated dynamically.

B The variable {{$guid}} is not recognized in pre-request scripts and returns the string literally.

C pm.variables.replaceIn() is asynchronous and needs await keyword.

D The console.log() statement causes the script to fail.

💡 Hint

Check how Postman handles dynamic variables in scripts.

In pre-request scripts, {{$guid}} used directly in a string is not replaced automatically. It returns the string '{{$guid}}' literally. To generate a UUID, you must use pm.variables.replaceIn('{{$guid}}') or a custom function.

🧠 Conceptual

advanced

What is the main advantage of using Postman dynamic variables for random data generation?

Why should testers prefer Postman dynamic variables like {{$randomInt}} or {{$randomEmail}} over hardcoded test data?

A They automatically validate the data format without assertions.

B They guarantee the same data every time for consistent test results.

C They help create unique test data each run, reducing false positives from duplicate data.

D They run faster than hardcoded data because they are cached.

💡 Hint

Think about test data uniqueness and test reliability.

Dynamic variables generate fresh random data each time, preventing conflicts like duplicate emails or IDs in tests. This reduces false failures caused by repeated data.

❓ framework

expert

Which Postman test script snippet correctly generates and validates a random date within the last 30 days?

You want to generate a random date within the last 30 days and verify it is not in the future. Which snippet does this correctly?

A

const now = new Date();
const past = new Date(now.getTime() - 30*24*60*60*1000);
const randomTime = past.getTime() + Math.random() * (now.getTime() - past.getTime());
const randomDate = new Date(randomTime);
pm.environment.set('randomDate', randomDate.toISOString());
pm.test('Date is not in future', () => { pm.expect(randomDate.getTime()).to.be.at.most(now.getTime()); });

B

const now = new Date();
const past = new Date(now.getTime() - 30*24*60*60*1000);
const randomTime = past.getTime() + Math.random() * (past.getTime() - now.getTime());
const randomDate = new Date(randomTime);
pm.environment.set('randomDate', randomDate.toISOString());
pm.test('Date is not in future', () => { pm.expect(randomDate.getTime()).to.be.at.most(now.getTime()); });

C

const now = new Date();
const past = new Date(now.getTime() - 30*24*60*60*1000);
const randomTime = past.getTime() - Math.random() * (now.getTime() - past.getTime());
const randomDate = new Date(randomTime);
pm.environment.set('randomDate', randomDate.toISOString());
pm.test('Date is not in future', () => { pm.expect(randomDate.getTime()).to.be.at.most(now.getTime()); });

D

const now = new Date();
const past = new Date(now.getTime() - 30*24*60*60*1000);
const randomTime = now.getTime() + Math.random() * (now.getTime() - past.getTime());
const randomDate = new Date(randomTime);
pm.environment.set('randomDate', randomDate.toISOString());
pm.test('Date is not in future', () => { pm.expect(randomDate.getTime()).to.be.at.most(now.getTime()); });

💡 Hint

Check how the randomTime is calculated between past and now timestamps.

Option A correctly calculates randomTime as a value between past.getTime() and now.getTime() by adding a random fraction of the difference to past.getTime(). Other options invert or misuse the range causing invalid dates.