Chaining request data in Postman - Framework Patterns

Framework Mode - Chaining request data

Folder Structure for Postman Test Collections

  PostmanProject/
  ├── collections/
  │   ├── UserManagement.postman_collection.json
  │   ├── OrderProcessing.postman_collection.json
  │   └── Authentication.postman_collection.json
  ├── environments/
  │   ├── Dev.postman_environment.json
  │   ├── Staging.postman_environment.json
  │   └── Production.postman_environment.json
  ├── scripts/
  │   ├── pre-request-scripts/
  │   │   └── authTokenSetup.js
  │   └── test-scripts/
  │       └── validateResponse.js
  ├── data/
  │   └── userData.json
  ├── reports/
  │   └── test-run-report.html
  └── postman_collection_runner.json
  

Test Framework Layers in Postman Chaining

• Collections: Group of API requests organized by feature or module.
• Requests: Individual API calls with URL, method, headers, body, and scripts.
• Pre-request Scripts: JavaScript code that runs before a request to set variables or prepare data.
• Tests: JavaScript assertions that run after a response to validate data and chain variables.
• Environments: Sets of variables for different deployment stages (dev, staging, prod).
• Data Files: External JSON or CSV files for data-driven testing.
• Reports: Output from test runs showing pass/fail results.

Configuration Patterns for Chaining Request Data

• Environment Variables: Store base URLs, tokens, and dynamic data per environment.
• Global Variables: Share data across collections if needed.
• Collection Variables: Variables scoped to a collection for chaining data within it.
• Pre-request Scripts: Use to generate or fetch tokens and set variables before requests.
• Test Scripts: Extract response data (like IDs or tokens) and save to variables for next requests.
• Data Files: Use with Collection Runner to run tests with multiple data sets.

Test Reporting and CI/CD Integration

• Newman CLI: Run Postman collections from command line for automation.
• HTML Reports: Generate readable reports using Newman reporters (html, junit).
• CI/CD Pipelines: Integrate Newman runs in Jenkins, GitHub Actions, GitLab CI to automate tests on code changes.
• Slack/Email Notifications: Configure to send test results after runs.
• Version Control: Store collections and environment files in Git for collaboration and history.

Best Practices for Chaining Request Data in Postman

1. Use Environment Variables: Keep environment-specific data outside requests for easy switching.
2. Extract and Save Data in Tests: Always parse response JSON and save needed values to variables for next requests.
3. Keep Requests Independent When Possible: Minimize dependencies but chain only when necessary to reflect real workflows.
4. Use Descriptive Variable Names: Make it clear what each variable stores to avoid confusion.
5. Modularize Collections: Group related requests and scripts to keep tests organized and maintainable.

Self Check Question

Where in this folder structure would you add a new script to extract a user ID from a login response and save it for later requests?

Key Result

Organize Postman collections with environment variables and scripts to chain request data smoothly.