Conditional request execution (setNextRequest) in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the next request executed?

Given this Postman test script, which request will run next after the current one?

Postman

if (pm.response.code === 200) {
    postman.setNextRequest('RequestB');
} else {
    postman.setNextRequest('RequestC');
}

A No next request will run; the collection stops

B RequestB if response code is 200, otherwise RequestC

C Always RequestB regardless of response code

D RequestC if response code is 200, otherwise RequestB

💡 Hint

Check the condition inside the if statement and what setNextRequest is called with.

The script checks if the response code is 200. If true, it sets the next request to 'RequestB'. Otherwise, it sets it to 'RequestC'.

❓ assertion

intermediate

Which assertion ensures the next request runs only on success?

You want the next request to run only if the current request succeeded (status 200). Which assertion and setNextRequest code is correct?

Postman

pm.test('Status is 200', function () {
    pm.response.to.have.status(200);
    postman.setNextRequest('NextRequest');
});

A Use pm.test to check status 200 and call setNextRequest inside it

B Call setNextRequest before pm.test assertion

C Call setNextRequest unconditionally outside pm.test

D Use pm.expect(pm.response.code).to.equal(200) without setNextRequest

💡 Hint

Where should setNextRequest be placed to run only if assertion passes?

Placing setNextRequest inside pm.test ensures it runs only if the test passes (status 200).

🔧 Debug

advanced

Why does setNextRequest not work as expected?

This script aims to skip the next request if a condition is false, but the next request still runs. What is the issue?

Postman

if (pm.response.json().success === false) {
    postman.setNextRequest(null);
}
// Next request still runs

A setNextRequest(null) is correct to stop execution; issue is elsewhere

B setNextRequest(null) must be called inside pm.test block to work

C setNextRequest(null) stops execution only if no other setNextRequest calls override it

D setNextRequest(null) should be setNextRequest('null') as string

💡 Hint

Check if other scripts or requests call setNextRequest after this code.

Calling setNextRequest(null) stops the collection run only if no other setNextRequest calls override it later.

🧠 Conceptual

advanced

What happens if setNextRequest is not called?

In a Postman collection run, if a request script does not call postman.setNextRequest, what happens after this request finishes?

A An error is thrown and the run aborts

B The collection run stops immediately

C The same request runs again in a loop

D The collection runs the next request in the defined order

💡 Hint

Think about default behavior when setNextRequest is not used.

If setNextRequest is not called, Postman runs the next request in the collection order by default.

❓ framework

expert

How to conditionally loop a request using setNextRequest?

You want to repeat 'RequestA' until a response field 'done' is true. Which script correctly implements this loop?

Postman

const done = pm.response.json().done;
if (!done) {
    postman.setNextRequest('RequestA');
} else {
    postman.setNextRequest(null);
}

A Loop while done is false by setting next request to 'RequestA', else stop with null

B Loop while done is true by setting next request to 'RequestA', else stop with null

C Always set next request to 'RequestA' regardless of done value

D Use postman.setNextRequest('null') as string to stop looping

💡 Hint

Check the condition logic and how setNextRequest controls looping.

The script loops by setting next request to 'RequestA' while done is false, stopping when done is true by setting null.