Iteration count in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the iteration count in Postman?

The iteration count is the number of times a Postman collection or request runs during a collection run. It helps test APIs multiple times with different data or scenarios.

beginner

How can you access the current iteration number in Postman scripts?

You can access it using pm.info.iteration. It starts from 0 for the first iteration and increases by 1 each time.

beginner

Why is iteration count useful in API testing?

It allows running the same test multiple times with different data sets, helping to find bugs that appear only in certain cases or after repeated calls.

beginner

How do you set the number of iterations in Postman?

When running a collection in the Collection Runner, you specify the number of iterations in the 'Iterations' input box before starting the run.

beginner

What will pm.info.iteration return on the third run if iterations start at 0?

It will return 2 because iteration counting starts at 0, so the first run is 0, second is 1, and third is 2.

In Postman, what does pm.info.iteration represent?

A The current iteration number starting from 0

B The total number of requests in the collection

C The number of failed tests

D The current request index

pm.info.iteration gives the current iteration count starting at 0 for the first run.

How do you specify how many times a collection runs in Postman Collection Runner?

A By modifying the test scripts

B By editing the request URL

C By changing environment variables

D By setting the 'Iterations' number before running

The 'Iterations' input in Collection Runner controls how many times the collection runs.

If you want to run a test 5 times with different data sets, what should you do in Postman?

A Run the collection once only

B Manually run the request 5 times

C Set iterations to 5 and use data files

D Change the request method to POST

Setting iterations to 5 and using a data file allows running tests with different data automatically.

What is the starting value of pm.info.iteration in Postman?

A 1

B 0

C -1

D Undefined

Iteration count starts at 0 for the first run in Postman.

Why might you use iteration count in your test scripts?

A To run different tests or data based on the iteration number

B To change the request URL automatically

C To skip tests randomly

D To stop the collection run early

You can use iteration count to customize tests or data for each run.

Explain how iteration count works in Postman and how you can use it in your tests.

Think about running the same test multiple times with different inputs.

Describe a real-life scenario where using iteration count in Postman would help improve API testing.

Imagine testing a login API with many usernames and passwords.

Practice

1. What does the iterationCount setting in Postman control?

easy

A. The number of requests in a collection

B. The number of times a collection or request runs automatically

C. The number of tests inside a single request

D. The number of environments available

Solution

1. Step 1: Understand the role of iterationCount

   The iterationCount defines how many times Postman runs the entire collection or request automatically.

2. Step 2: Differentiate from other counts

   It is not about the number of requests or tests, but how many times the run repeats.

3. Final Answer:

   The number of times a collection or request runs automatically -> Option B

4. Quick Check:

   iterationCount = run times [OK]

Hint: iterationCount means how many times to run tests [OK]

Common Mistakes:

• Confusing iterationCount with number of requests
• Thinking iterationCount counts tests inside a request
• Mixing iterationCount with environment count

2. Which of the following is the correct way to set iteration count to 5 in Postman Collection Runner?

easy

A. Set iterationCount = 5 in the pre-request script

B. Set environment variable iterationCount to 5

C. Add pm.iterationCount = 5 in the test script

D. Enter 5 in the 'Iterations' field of the Collection Runner UI

Solution

1. Step 1: Identify how to set iteration count in Postman UI

   The Collection Runner has an 'Iterations' input field where you specify how many times to run.

2. Step 2: Understand script limitations

   Setting iterationCount in scripts or environment variables does not control the runner's iteration count.

3. Final Answer:

   Enter 5 in the 'Iterations' field of the Collection Runner UI -> Option D

4. Quick Check:

   Use Collection Runner UI to set iterations [OK]

Hint: Set iterations number in Collection Runner UI field [OK]

Common Mistakes:

• Trying to set iterationCount in scripts
• Confusing environment variables with runner settings
• Assuming iterationCount is a pm API property

3. Consider this test script in Postman run with iterationCount = 3:

console.log(pm.info.iteration);
pm.test('Check iteration', () => {
  pm.expect(pm.info.iteration).to.be.below(3);
});

What will be the console output and test result for each iteration?

medium

A. Console logs 0,1,2; last test fails

B. Console logs 1,2,3; last test fails

C. Console logs 0,1,2; all tests pass

D. Console logs 1,2,3; all tests pass

Solution

1. Step 1: Understand pm.info.iteration values

   Iteration count starts at 0, so for 3 iterations, values are 0, 1, 2.

2. Step 2: Check test condition pm.expect(pm.info.iteration).to.be.below(3)

   All iteration values (0,1,2) are less than 3, so all tests pass.

3. Final Answer:

   Console logs 0,1,2; all tests pass -> Option C

4. Quick Check:

   Iteration index starts at 0 and is below count [OK]

Hint: Iteration index starts at 0, less than iterationCount [OK]

Common Mistakes:

• Assuming iteration starts at 1
• Expecting iteration to equal iterationCount
• Confusing iterationCount with max iteration index

4. You wrote this pre-request script to stop running after 3 iterations:

if (pm.info.iterationCount > 3) {
  postman.setNextRequest(null);
}

Why does the collection keep running beyond 3 iterations?

medium

A. pm.info.iterationCount is total iterations, not current iteration index

B. postman.setNextRequest(null) does not stop iterations

C. pm.info.iterationCount is read-only and cannot be used in conditions

D. The script syntax is incorrect and causes error

Solution

1. Step 1: Understand pm.info.iterationCount meaning

   pm.info.iterationCount is the total number of iterations set, not the current iteration number.

2. Step 2: Identify correct property for current iteration

   The current iteration index is pm.info.iteration, which starts at 0.

3. Final Answer:

   pm.info.iterationCount is total iterations, not current iteration index -> Option A

4. Quick Check:

   Use pm.info.iteration to check current iteration [OK]

Hint: Use pm.info.iteration for current run, not iterationCount [OK]

Common Mistakes:

• Confusing iterationCount with iteration index
• Expecting setNextRequest(null) to stop all iterations
• Using wrong property names in conditions

5. You want to run a Postman collection 4 times, but skip iteration 2 (zero-based). Which script in the pre-request script will achieve this?

hard

A. if (pm.info.iteration === 2) { postman.setNextRequest(null); }

B. if (pm.info.iteration === 2) { postman.setNextRequest(pm.info.requestName); }

C. if (pm.info.iteration === 2) { postman.setNextRequest('Request1'); }

D. if (pm.info.iteration === 2) { postman.setNextRequest('Request3'); }

Solution

1. Step 1: Identify how to skip an iteration

   To skip iteration 2, we stop the run at that iteration by setting next request to null.

2. Step 2: Use correct condition and method

   Check if current iteration is 2, then call postman.setNextRequest(null) to stop further requests in that iteration.

3. Final Answer:

   if (pm.info.iteration === 2) { postman.setNextRequest(null); } -> Option A

4. Quick Check:

   Set next request null to skip iteration [OK]

Hint: Use setNextRequest(null) on iteration to skip it [OK]

Common Mistakes:

• Setting next request to current or wrong request name
• Confusing iteration index with iterationCount
• Not stopping requests properly to skip iteration