Why chaining simulates real workflows in Postman - Automation Benefits in Action

Automate API request chaining to simulate real workflows

Preconditions (3)

Step 1: Send a POST request to create a new user with valid data

Step 2: Extract the user ID from the create user response

Step 3: Send a GET request to retrieve the user details using the extracted user ID

Step 4: Verify the user details response contains the correct user information

✅ Expected Result: The GET request returns user details matching the created user, confirming chaining simulates real workflows

Automation Requirements - Postman Tests (JavaScript)

Assertions Needed:

Verify POST response status is 201

Verify user ID is extracted and not null

Verify GET response status is 200

Verify GET response body contains expected user data

Best Practices:

Use pm.sendRequest for chaining requests

Use pm.expect for assertions

Extract variables using pm.response.json()

Keep tests readable and maintainable

Automated Solution

Postman

pm.test('Create user and chain to get user details', function () {
    pm.sendRequest({
        url: 'https://api.example.com/users',
        method: 'POST',
        header: {
            'Content-Type': 'application/json'
        },
        body: {
            mode: 'raw',
            raw: JSON.stringify({ name: 'John Doe', email: '[e-mail]' })
        }
    }, function (err, res) {
        pm.expect(err).to.be.null;
        pm.expect(res).to.have.property('code', 201);
        const userId = res.json().id;
        pm.expect(userId).to.be.a('string').that.is.not.empty;

        pm.sendRequest({
            url: `https://api.example.com/users/${userId}`,
            method: 'GET'
        }, function (err2, res2) {
            pm.expect(err2).to.be.null;
            pm.expect(res2).to.have.property('code', 200);
            const user = res2.json();
            pm.expect(user).to.have.property('name', 'John Doe');
            pm.expect(user).to.have.property('email', '[e-mail]');
        });
    });
});

This test script uses Postman’s pm.sendRequest to chain two API calls, simulating a real workflow.

First, it sends a POST request to create a user and checks the response status is 201 (Created).

Then, it extracts the id from the response JSON and verifies it is a non-empty string.

Next, it sends a GET request using the extracted id to retrieve user details.

Finally, it asserts the GET response status is 200 (OK) and the returned user data matches the created user.

This chaining simulates how real applications use data from one API call in the next, ensuring workflows are tested end-to-end.

Common Mistakes - 3 Pitfalls

Not waiting for the first request to complete before sending the second

Hardcoding user ID instead of extracting from response

Not checking response status codes before proceeding

Bonus Challenge

Now add data-driven testing with 3 different user data inputs for creation and verify each workflow

Show Hint

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