Iteration count in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the iteration count value after the 3rd request?

In Postman, you run a collection with 5 iterations. You use this script in the Tests tab:

pm.test("Check iteration", () => {
    pm.expect(pm.info.iteration).to.be.a('number');
});

What is the value of pm.info.iteration during the 3rd request?

A 2

B 3

C 0

D 1

💡 Hint

Remember, iteration count starts at zero in Postman.

Postman counts iterations starting from 0. So the first request is iteration 0, second is 1, third is 2, and so on.

❓ assertion

intermediate

Which assertion correctly checks the iteration count is less than 5?

You want to write a test in Postman to verify the current iteration count is less than 5. Which assertion is correct?

A pm.test('Iteration less than 5', () => { pm.expect(pm.info.iteration).to.be.below(5); });

B pm.test('Iteration less than 5', () => { pm.expect(pm.info.iteration < 5); });

C pm.test('Iteration less than 5', () => { pm.expect(pm.info.iteration <= 5); });

D pm.test('Iteration less than 5', () => { pm.expect(pm.info.iteration).to.be.lessThan(5); });

💡 Hint

Check the syntax for Chai assertions in Postman.

Option A uses the correct Chai assertion to.be.below(5) to check if iteration is less than 5.

Option A uses lessThan which is not a valid Chai method.

Options B and C misuse pm.expect by passing a boolean expression instead of a value.

🔧 Debug

advanced

Why does pm.info.iteration always show 0 in your tests?

You run a Postman collection with multiple iterations, but your test script always logs pm.info.iteration as 0. What is the most likely reason?

A The iteration count resets to 0 after each request in the collection.

B You are running the request individually, not as part of a collection run with iterations.

C pm.info.iteration is only available in the Pre-request Script tab, not Tests tab.

D You need to enable iteration count in Postman settings before it works.

💡 Hint

Think about how Postman handles iteration count when running single requests vs collection runs.

pm.info.iteration is only set during collection runs with multiple iterations. Running a single request manually always shows iteration 0.

🧠 Conceptual

advanced

What does pm.info.iteration represent in Postman?

Choose the best description of pm.info.iteration in Postman scripts.

A The number of times the current request has been retried.

B The total number of iterations completed so far in the collection run.

C The number of requests sent in the current iteration.

D The zero-based index of the current iteration in a collection run.

💡 Hint

Think about what iteration means in a collection run context.

pm.info.iteration is the zero-based index of the current iteration during a collection run. It does not count total iterations completed or retries.

❓ framework

expert

How to run a Postman collection exactly 10 times using Newman CLI?

You want to run a Postman collection 10 times in a row using Newman from the command line. Which command correctly sets the iteration count?

A newman run collection.json --count 10

B newman run collection.json --iterations 10

C newman run collection.json --iteration-count 10

D newman run collection.json --repeat 10

💡 Hint

Check Newman CLI documentation for the correct flag to set iteration count.

The correct Newman CLI option to specify the number of iterations is --iteration-count. Other options are invalid and cause errors.