Conditional request execution (setNextRequest) in Postman - Framework Patterns

Framework Mode - Conditional request execution (setNextRequest)

Folder Structure

Postman Collection
├── Folder: Authentication
│   ├── Request: Login
│   └── Request: Refresh Token
├── Folder: User Management
│   ├── Request: Get User
│   ├── Request: Update User
│   └── Request: Delete User
├── Folder: Conditional Flows
│   ├── Request: Check User Status
│   ├── Request: Activate User
│   └── Request: Notify User
└── Environment Files
    ├── dev.postman_environment.json
    ├── staging.postman_environment.json
    └── prod.postman_environment.json
  

Test Framework Layers

• Pre-request Scripts: Prepare data or set variables before a request runs.
• Requests: API calls organized in folders representing features or flows.
• Test Scripts: Validate responses and control flow using pm.setNextRequest().
• Environment & Globals: Store variables like tokens, URLs, and flags for conditional logic.
• Collection Runner / Monitor: Executes requests in order, respects setNextRequest() to jump or skip requests.

Configuration Patterns

• Environment Files: Separate files for dev, staging, prod with URLs and credentials.
• Global Variables: For flags controlling conditional execution across requests.
• Pre-request Scripts: Set or reset variables to control which request runs next.
• Using pm.setNextRequest(): Dynamically decide next request based on response data or variables.

Test Reporting and CI/CD Integration

• Newman CLI: Run Postman collections in CI pipelines with detailed JSON or HTML reports.
• Conditional Execution Logs: Use console.log() in scripts to trace which requests ran.
• Fail Fast: Use test assertions to stop execution on failures by controlling setNextRequest().
• Integrate with CI/CD: Automate collection runs on code push, environment changes, or schedule.

Best Practices

1. Clear Naming: Name requests clearly to use in setNextRequest() calls.
2. Reset Flow: At the end of a flow, call pm.setNextRequest(null) to stop execution cleanly.
3. Use Variables: Store decision flags in environment or globals for flexible control.
4. Keep Logic Simple: Avoid complex nested conditions; split flows into folders if needed.
5. Log Decisions: Use console.log() to track which path the flow took during runs.

Self Check

Where would you add a new request that runs only if a user is inactive, using pm.setNextRequest() to conditionally execute it?

Key Result

Use pm.setNextRequest() in Postman test scripts to control conditional request execution dynamically within collections.