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.

Practice

1. What is the main purpose of chaining request data in Postman?

easy

A. To pass data from one API request to another for connected testing

B. To run multiple requests at the same time

C. To change the request method automatically

D. To generate random data for each request

Solution

1. Step 1: Understand chaining request data

   Chaining request data means using data from one API response in the next request to keep tests connected.

2. Step 2: Identify the purpose

   This helps simulate real user flows where one action depends on the previous one.

3. Final Answer:

   To pass data from one API request to another for connected testing -> Option A

4. Quick Check:

   Chaining = passing data between requests [OK]

Hint: Chaining means passing data forward between requests [OK]

Common Mistakes:

• Thinking chaining runs requests simultaneously
• Confusing chaining with changing HTTP methods
• Assuming chaining generates random data

2. Which Postman script correctly saves a value from a JSON response to an environment variable named userId?

easy

A. pm.response.set('userId', pm.environment.json().id);

B. pm.environment.get('userId', pm.response.json().id);

C. pm.response.get('userId', pm.environment.json().id);

D. pm.environment.set('userId', pm.response.json().id);

Solution

1. Step 1: Identify correct method to save variable

   Use pm.environment.set(key, value) to save data to environment variables.

2. Step 2: Extract value from response JSON

   Use pm.response.json() to parse JSON and get the id field.

3. Final Answer:

   pm.environment.set('userId', pm.response.json().id); -> Option D

4. Quick Check:

   Set environment variable = pm.environment.set [OK]

Hint: Use pm.environment.set to save data from pm.response.json() [OK]

Common Mistakes:

• Using pm.environment.get to set a variable
• Confusing pm.response and pm.environment methods
• Trying to get data from environment instead of response

3. Given this Postman test script after a request:

const jsonData = pm.response.json();
pm.environment.set('token', jsonData.auth.token);

What will be the value of the environment variable token if the response JSON is {"auth": {"token": "abc123"}}?

medium

A. null

B. undefined

C. "abc123"

D. Error: token not found

Solution

1. Step 1: Parse the response JSON

   The response JSON has an object with auth containing token with value "abc123".

2. Step 2: Set environment variable

   The script sets token variable to jsonData.auth.token, which is "abc123".

3. Final Answer:

   "abc123" -> Option C

4. Quick Check:

   token value = "abc123" [OK]

Hint: Check JSON path matches response structure exactly [OK]

Common Mistakes:

• Assuming token is undefined if nested
• Forgetting to parse JSON before accessing
• Expecting error when token exists

4. You wrote this script to chain data:

const data = pm.response.json();
pm.environment.set('userId', data.user.id);

But the environment variable userId is always empty after the request. What is the likely problem?

medium

A. The script must run before the request

B. The response JSON does not have a user object

C. You must use pm.variables.set instead

D. pm.environment.set cannot save variables

Solution

1. Step 1: Check JSON structure

   If data.user is undefined, accessing data.user.id returns undefined, so variable is empty.

2. Step 2: Confirm environment.set works correctly

   pm.environment.set works if given a valid value, so problem is likely missing user in response.

3. Final Answer:

   The response JSON does not have a user object -> Option B

4. Quick Check:

   Missing JSON key = empty variable [OK]

Hint: Verify JSON keys exist before accessing nested values [OK]

Common Mistakes:

• Assuming pm.environment.set is broken
• Using wrong method like pm.variables.set
• Running script before response is received

5. You want to chain two requests where the first returns a list of users:

{"users": [{"id": 1}, {"id": 2}]}

You want to save the id of the first user to an environment variable firstUserId and use it in the second request URL as /users/{{firstUserId}}. Which script correctly does this in the first request's Tests tab?

hard

A. const jsonData = pm.response.json();
pm.environment.set('firstUserId', jsonData.users[0].id);

B. const jsonData = pm.response.json();
pm.environment.set('firstUserId', jsonData.users.id[0]);

C. const jsonData = pm.response.json();
pm.environment.set('firstUserId', jsonData.users[1].id);

D. const jsonData = pm.response.json();
pm.environment.set('firstUserId', jsonData.user[0].id);

Solution

1. Step 1: Parse response JSON correctly

   The response has a users array with objects containing id. The first user is at index 0.

2. Step 2: Save first user's id properly

   Access jsonData.users[0].id and save it with pm.environment.set.

3. Final Answer:

   const jsonData = pm.response.json(); pm.environment.set('firstUserId', jsonData.users[0].id); -> Option A

4. Quick Check:

   Array index 0 for first user id [OK]

Hint: Use array index [0] to get first item in JSON array [OK]

Common Mistakes:

• Using wrong array index or property name
• Accessing id as users.id[0] instead of users[0].id
• Using singular 'user' instead of 'users'