Run order and flow control in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of run order in Postman collections?

Run order defines the sequence in which requests or folders execute within a Postman collection. It ensures tests run in a logical flow, like following steps in a recipe.

intermediate

How can you control the flow between requests in Postman?

You can control flow using scripts with commands like pm.setNextRequest() to jump to a specific request or skip others, similar to choosing your own adventure in a story.

beginner

What happens if postman.setNextRequest(null) is used in a test script?

It stops the collection run immediately after the current request, like pressing pause on a playlist.

intermediate

Explain the difference between folder run order and request run order in Postman.

Folder run order is the sequence of folders in a collection, while request run order is the sequence of requests inside each folder. Think of folders as chapters and requests as pages.

beginner

Why is flow control important in automated API testing?

Flow control ensures tests run in the right order, handle dependencies, and react to results. It prevents errors like trying to use data before it exists, similar to following steps in a recipe carefully.

In Postman, which method is used to jump to a specific request during a collection run?

A postman.setNextRequest()

B postman.skipRequest()

C postman.runRequest()

D postman.next()

The method postman.setNextRequest() directs Postman to run a specific request next.

What does setting postman.setNextRequest(null) do in a Postman test script?

A Restarts the collection run

B Skips the next request

C Runs the next request twice

D Stops the collection run

Setting postman.setNextRequest(null) stops the collection run immediately.

Which of the following best describes run order in Postman?

A Sequential execution of requests and folders

B Random execution of requests

C Execution based on request size

D Execution only of failed requests

Run order means requests and folders run one after another in a set sequence.

How can you skip a request conditionally in Postman?

A Delete the request

B Use <code>postman.skipRequest()</code>

C Use <code>postman.setNextRequest()</code> to jump over it

D Disable the request manually

You can skip requests by setting the next request to one after the current, using postman.setNextRequest().

If you want to run all requests in a folder before moving to the next folder, what controls this behavior?

A Request run order inside the folder

B Both A and B

C Folder run order in the collection

D Postman randomizes order automatically

Both folder run order and request run order inside folders control the sequence.

Describe how you can control the flow of requests in a Postman collection run.

Think about how to jump to specific requests or stop running.

Explain why managing run order and flow control is important in automated API testing.

Consider what happens if tests run in the wrong order.

Practice

1. In Postman, what does pm.setNextRequest() do in a collection run?

easy

A. It sets which request runs next in the collection.

B. It stops the entire collection run immediately.

C. It restarts the current request.

D. It logs the response of the current request.

Solution

1. Step 1: Understand the purpose of pm.setNextRequest()

   This function controls the flow by specifying the next request to run in the collection.

2. Step 2: Compare other options

   Stopping the run is done by pm.setNextRequest(null), not this function. Restarting or logging are unrelated.

3. Final Answer:

   It sets which request runs next in the collection. -> Option A

4. Quick Check:

   Flow control = set next request [OK]

Hint: Remember: setNextRequest controls next request flow [OK]

Common Mistakes:

• Confusing pm.setNextRequest() with stopping the run
• Thinking it restarts the current request
• Assuming it logs data instead of controlling flow

2. Which of the following is the correct syntax to stop running any further requests in a Postman collection?

easy

A. pm.abortRun()

B. pm.setNextRequest('stop')

C. pm.stopCollection()

D. pm.setNextRequest(null)

Solution

1. Step 1: Identify the method to stop collection run

   Postman uses pm.setNextRequest(null) to stop running further requests.

2. Step 2: Verify other options

   Other options like pm.stopCollection() or pm.abortRun() do not exist in Postman scripting.

3. Final Answer:

   pm.setNextRequest(null) -> Option D

4. Quick Check:

   Stop run = setNextRequest(null) [OK]

Hint: Use null in setNextRequest to stop run [OK]

Common Mistakes:

• Using a string like 'stop' instead of null
• Assuming non-existent functions stop the run
• Confusing stopping with skipping requests

3. Consider this Postman test script inside a request named 'Request A':

if (pm.response.code === 200) {
  pm.setNextRequest('Request B');
} else {
  pm.setNextRequest(null);
}

What happens if the response code is 404?

medium

A. The collection run continues to 'Request B'.

B. An error is thrown and the run fails.

C. The collection run stops after 'Request A'.

D. The collection run restarts from the first request.

Solution

1. Step 1: Analyze the condition for response code 404

   Since 404 is not 200, the else block runs pm.setNextRequest(null).

2. Step 2: Understand effect of pm.setNextRequest(null)

   This stops the collection run immediately after the current request.

3. Final Answer:

   The collection run stops after 'Request A'. -> Option C

4. Quick Check:

   404 triggers stop = setNextRequest(null) [OK]

Hint: If condition false, setNextRequest(null) stops run [OK]

Common Mistakes:

• Assuming it continues to next request regardless
• Thinking it restarts the collection
• Believing an error is thrown automatically

4. You wrote this test script in Postman:

pm.setNextRequest('Request C');
pm.setNextRequest(null);

What is the effect on the collection run flow?

medium

A. The run jumps to 'Request C' and then stops.

B. The run stops immediately; 'Request C' is skipped.

C. The run ignores both commands and continues normally.

D. The run loops infinitely between requests.

Solution

1. Step 1: Understand order of pm.setNextRequest calls

   Only the last pm.setNextRequest() call takes effect in a single script execution.

2. Step 2: Analyze the last call pm.setNextRequest(null)

   This stops the collection run immediately, ignoring previous setNextRequest calls.

3. Final Answer:

   The run stops immediately; 'Request C' is skipped. -> Option B

4. Quick Check:

   Last setNextRequest call wins = null stops run [OK]

Hint: Last setNextRequest call controls flow [OK]

Common Mistakes:

• Thinking both calls run in sequence
• Assuming first call overrides last
• Believing it causes infinite loops

5. You want to run a Postman collection where:
- If 'Login' request succeeds (status 200), run 'GetData'.
- If 'Login' fails, stop the run.
- After 'GetData', always run 'Logout'.

Which sequence of pm.setNextRequest() calls in the 'Login' and 'GetData' test scripts achieves this flow?

hard

A. In 'Login': pm.setNextRequest('GetData') if 200 else pm.setNextRequest(null);In 'GetData': pm.setNextRequest('Logout')

B. In 'Login': pm.setNextRequest('Logout') always;In 'GetData': pm.setNextRequest(null)

C. In 'Login': pm.setNextRequest(null) always;In 'GetData': pm.setNextRequest('Logout')

D. In 'Login': pm.setNextRequest('GetData') always;In 'GetData': pm.setNextRequest(null)

Solution

1. Step 1: Control flow after 'Login'

   If status is 200, next request should be 'GetData'; else stop run with pm.setNextRequest(null).

2. Step 2: Control flow after 'GetData'

   Always run 'Logout' next, so pm.setNextRequest('Logout') is set in 'GetData' tests.

3. Final Answer:

   In 'Login': pm.setNextRequest('GetData') if 200 else pm.setNextRequest(null); In 'GetData': pm.setNextRequest('Logout') -> Option A

4. Quick Check:

   Conditional jump + final logout = In 'Login': pm.setNextRequest('GetData') if 200 else pm.setNextRequest(null);
   In 'GetData': pm.setNextRequest('Logout') [OK]

Hint: Use conditional setNextRequest in Login, fixed next in GetData [OK]

Common Mistakes:

• Setting wrong next request after Login
• Not stopping run on Login failure
• Skipping Logout after GetData