Why chaining simulates real workflows in Postman - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the environment variable with the response value.

Postman

pm.environment.set('userId', [1]);

Drag options to blanks, or click blank then click option'

Apm.request.url

Bpm.response.text()

Cpm.response.json().id

Dpm.environment.get('userId')

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.response.text() returns raw text, not parsed JSON.

Trying to get variable from environment instead of response.

The correct way to get a value from the JSON response is using pm.response.json().id. This sets the environment variable userId for chaining.

2fill in blank

medium

Complete the code to use the environment variable in the next request URL.

Postman

pm.request.url = `https://api.example.com/users/$[1]`;

Drag options to blanks, or click blank then click option'

Apm.environment.get('userId')

Bpm.response.json().id

Cpm.variables.get('userId')

Dpm.request.body

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.response.json() here is wrong because this is a new request.

Using pm.variables.get() may not access environment variables.

To use the stored variable in the request URL, use pm.environment.get('userId') which retrieves the value set earlier.

3fill in blank

hard

Fix the error in the test script to correctly check the response status code.

Postman

pm.test('Status code is 200', function () { pm.response.to.have.status([1]); });

Drag options to blanks, or click blank then click option'

A200

B"200"

Cpm.response.code

D'200'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '200' or "200" as string causes assertion failure.

Using pm.response.code is not valid here.

The status code should be a number, so 200 without quotes is correct. Using quotes makes it a string, causing the test to fail.

4fill in blank

hard

Fill both blanks to extract 'token' from response and set it as a global variable.

Postman

const token = pm.response.json().[1];
pm.globals.set('[2]', token);

Drag options to blanks, or click blank then click option'

Atoken

BauthToken

CaccessToken

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong property name like 'id' or 'accessToken'.

Setting environment variable instead of global.

The response JSON property is 'token', and the global variable name to set is 'authToken'. This allows chaining with a global token.

5fill in blank

hard

Fill all three blanks to create a test that checks if the response JSON has a 'success' property set to true.

Postman

pm.test('Response success is true', function () {
  const jsonData = pm.response.[1]();
  pm.expect(jsonData.[2]).to.eql([3]);
});

Drag options to blanks, or click blank then click option'

Ajson

Bsuccess

Ctrue

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.response.text() returns string, not JSON.

Checking 'success' as string 'true' instead of boolean true.

Use pm.response.json() to parse JSON, check the 'success' property, and expect it to equal true (boolean).

Practice

1. Why is chaining requests in Postman important for testing workflows?

easy

A. It speeds up the execution by running all requests in parallel.

B. It simulates real user actions by linking multiple requests step-by-step.

C. It automatically generates test data without user input.

D. It only tests individual requests without dependencies.

Solution

1. Step 1: Understand chaining concept

   Chaining means connecting requests so output from one is input to another, like real user steps.

2. Step 2: Identify why chaining matters

   This simulates real workflows where actions depend on previous results, catching issues in multi-step processes.

3. Final Answer:

   It simulates real user actions by linking multiple requests step-by-step. -> Option B

4. Quick Check:

   Chaining = simulating workflows [OK]

Hint: Chaining links requests like real user steps [OK]

Common Mistakes:

• Thinking chaining runs requests in parallel
• Believing chaining auto-generates data
• Assuming chaining tests requests independently

2. Which Postman feature is used to pass data from one request to another in a chain?

easy

A. Environment variables

B. Response body

C. Collection runner

D. Pre-request scripts

Solution

1. Step 1: Identify data passing method

   Environment variables store data accessible across requests in a collection.

2. Step 2: Understand chaining data flow

   Data saved in environment variables from one request can be used in the next, enabling chaining.

3. Final Answer:

   Environment variables -> Option A

4. Quick Check:

   Data passing = Environment variables [OK]

Hint: Use environment variables to share data between requests [OK]

Common Mistakes:

• Confusing pre-request scripts with data storage
• Thinking collection runner passes data automatically
• Assuming response body alone passes data

3. Given this Postman test script snippet in Request 1:

pm.environment.set('token', pm.response.json().authToken);

And in Request 2 header:

Authorization: Bearer {{token}}

What happens when these requests run in a chain?

medium

A. Request 2 uses the token from Request 1's response for authorization.

B. Request 2 fails because token is not set before it runs.

C. Request 1 overwrites the token after Request 2 runs.

D. Request 2 sends an empty Authorization header.

Solution

1. Step 1: Analyze token setting in Request 1

   Request 1 saves authToken from its response into environment variable 'token'.

2. Step 2: Check usage in Request 2

   Request 2 uses {{token}} in Authorization header, so it uses the saved token from Request 1.

3. Final Answer:

   Request 2 uses the token from Request 1's response for authorization. -> Option A

4. Quick Check:

   Token saved then used = Authorization works [OK]

Hint: Set variable in one request, use it in next [OK]

Common Mistakes:

• Assuming variables update after all requests run
• Thinking token is empty without manual setting
• Confusing order of request execution

4. You chained two requests in Postman, but the second request fails with a 401 Unauthorized error. What is the most likely cause?

medium

A. The first request did not return any response.

B. The second request URL is incorrect.

C. The collection runner is not enabled.

D. The environment variable holding the token was not set correctly in the first request.

Solution

1. Step 1: Understand 401 error meaning

   401 Unauthorized means missing or invalid authentication token in the second request.

2. Step 2: Check chaining token setup

   If the environment variable token was not set in the first request, the second request sends no valid token, causing failure.

3. Final Answer:

   The environment variable holding the token was not set correctly in the first request. -> Option D

4. Quick Check:

   401 error = missing token [OK]

Hint: Check token variable set before second request [OK]

Common Mistakes:

• Blaming URL without checking auth token
• Thinking collection runner affects token passing
• Ignoring first request response content

5. You want to test a multi-step user signup and login flow in Postman using chaining. Which approach best simulates this real workflow?

hard

A. Use only the login request with hardcoded credentials.

B. Run signup and login requests separately without sharing data.

C. Chain requests where signup saves user ID, then login uses that ID to authenticate.

D. Run signup request multiple times without login.

Solution

1. Step 1: Understand multi-step flow

   User signup creates a user ID needed for login authentication.

2. Step 2: Apply chaining to pass data

   Chaining saves user ID from signup response and uses it in login request to simulate real user flow.

3. Final Answer:

   Chain requests where signup saves user ID, then login uses that ID to authenticate. -> Option C

4. Quick Check:

   Chaining passes data to simulate workflow [OK]

Hint: Pass data stepwise to mimic user actions [OK]

Common Mistakes:

• Testing requests independently without data sharing
• Using hardcoded data ignoring dynamic flow
• Skipping login after signup