Why organizing requests improves workflow in Postman - Automation Benefits in Action

Organize API requests into folders and verify workflow improvement

Preconditions (2)

Step 1: Open the existing collection with multiple API requests

Step 2: Create a new folder inside the collection named 'User Management'

Step 3: Drag and drop all user-related API requests into the 'User Management' folder

Step 4: Create another folder named 'Product Management'

Step 5: Move all product-related API requests into the 'Product Management' folder

Step 6: Save the collection

Step 7: Open the 'User Management' folder and run all requests sequentially

Step 8: Observe the order and ease of running grouped requests

Step 9: Open the 'Product Management' folder and run all requests sequentially

Step 10: Observe the order and ease of running grouped requests

✅ Expected Result: API requests are grouped logically into folders, making it easier to find and run related requests. Running requests in folders improves workflow by reducing time spent searching and organizing requests.

Automation Requirements - Postman Collection Runner with Newman

Assertions Needed:

Verify that requests are executed in the order defined by folders

Verify that all requests in 'User Management' folder return status code 200

Verify that all requests in 'Product Management' folder return status code 200

Best Practices:

Use folder structure in Postman collections to group related requests

Use Newman CLI to run collections and folders programmatically

Use assertions in Postman tests to validate response status and data

Keep collection organized for maintainability and collaboration

Automated Solution

Postman

const newman = require('newman');

// Run the 'User Management' folder
newman.run({
    collection: require('./MyCollection.json'),
    folder: 'User Management',
    reporters: 'cli'
}, function (err, summary) {
    if (err) { throw err; }
    const failures = summary.run.failures;
    if (failures.length > 0) {
        console.error('Some requests in User Management folder failed');
        process.exit(1);
    } else {
        console.log('All User Management requests passed');

        // After success, run the 'Product Management' folder
        newman.run({
            collection: require('./MyCollection.json'),
            folder: 'Product Management',
            reporters: 'cli'
        }, function (err2, summary2) {
            if (err2) { throw err2; }
            const failures2 = summary2.run.failures;
            if (failures2.length > 0) {
                console.error('Some requests in Product Management folder failed');
                process.exit(1);
            } else {
                console.log('All Product Management requests passed');
            }
        });
    }
});

This script uses Newman, the command-line tool for running Postman collections.

First, it runs all requests inside the 'User Management' folder. It checks if any request failed by inspecting summary.run.failures. If any request fails, it stops and reports the failure.

If all requests pass, it proceeds to run the 'Product Management' folder similarly.

This approach shows how organizing requests into folders allows running related requests together, improving workflow and test clarity.

Using Newman with folder option ensures only grouped requests run, matching the manual test case steps.

Common Mistakes - 3 Pitfalls

{'mistake': 'Running the entire collection without using folders', 'why_bad': 'It ignores the benefit of grouping requests, making it harder to isolate and run related tests.', 'correct_approach': "Use the 'folder' option in Newman to run specific groups of requests."}

Hardcoding request URLs or data inside the automation script

Not checking for failures after running requests

Bonus Challenge

Now add data-driven testing by running the 'User Management' folder with 3 different sets of environment variables

Show Hint

Practice

1. Why is organizing API requests into collections and folders important in Postman?

easy

A. It makes the requests run faster on the server.

B. It helps save time by grouping related requests together.

C. It automatically fixes errors in the requests.

D. It hides requests from team members.

Solution

1. Step 1: Understand the purpose of organizing requests

   Organizing requests groups related API calls, making them easier to find and manage.

2. Step 2: Identify the benefit in workflow

   Grouping saves time and effort by avoiding searching through many unrelated requests.

3. Final Answer:

   It helps save time by grouping related requests together. -> Option B

4. Quick Check:

   Organizing = Saves time [OK]

Hint: Organize to save time and find requests faster [OK]

Common Mistakes:

• Thinking organization speeds up server response
• Believing organization fixes request errors automatically
• Assuming organization hides requests from teammates

2. Which of the following is the correct way to create a folder inside a Postman collection?

easy

A. Click 'New' and choose 'Environment'.

B. Rename the collection to a folder name.

C. Drag a request outside the collection.

D. Right-click the collection and select 'Add Folder'.

Solution

1. Step 1: Recall how to add folders in Postman

   Folders are added by right-clicking a collection and selecting 'Add Folder'.

2. Step 2: Eliminate incorrect options

   Creating an environment or dragging requests outside does not create folders; renaming collection changes its name, not structure.

3. Final Answer:

   Right-click the collection and select 'Add Folder'. -> Option D

4. Quick Check:

   Add folder = Right-click collection [OK]

Hint: Right-click collection to add folders quickly [OK]

Common Mistakes:

• Choosing 'Environment' instead of 'Folder'
• Dragging requests outside collections
• Renaming collections to create folders

3. Consider this scenario: You have 10 API requests in one collection without folders. What is the likely impact on your workflow?

medium

A. It will be easy to find requests quickly.

B. Requests will run faster without folders.

C. It may cause confusion and slow down finding requests.

D. Postman will automatically group requests for you.

Solution

1. Step 1: Analyze the effect of no folders in a collection

   Without folders, many requests appear in one list, making it harder to find specific ones.

2. Step 2: Understand workflow impact

   This confusion slows down the process of selecting and running requests.

3. Final Answer:

   It may cause confusion and slow down finding requests. -> Option C

4. Quick Check:

   No folders = Confusion and slow search [OK]

Hint: No folders means harder to find requests fast [OK]

Common Mistakes:

• Assuming no folders improve speed
• Believing Postman auto-groups requests
• Thinking all requests are always easy to find

4. You created folders in a Postman collection but cannot find some requests inside them. What is the most likely reason?

medium

A. Requests were not moved into the folders after creation.

B. Folders automatically delete requests after creation.

C. Postman does not support folders inside collections.

D. Requests are hidden by default in folders.

Solution

1. Step 1: Understand folder behavior in Postman

   Folders organize requests but do not automatically move existing requests inside them.

2. Step 2: Identify why requests are missing

   If requests are not manually moved, they remain outside folders and may be overlooked.

3. Final Answer:

   Requests were not moved into the folders after creation. -> Option A

4. Quick Check:

   Requests must be moved manually [OK]

Hint: Move requests into folders manually after creating folders [OK]

Common Mistakes:

• Thinking folders delete requests
• Believing Postman lacks folder support
• Assuming requests hide automatically

5. You have a large API project with hundreds of requests. How should you organize them in Postman to improve teamwork and clarity?

hard

A. Create multiple collections for different modules and use folders inside each collection to group related requests.

B. Keep all requests in one collection without folders to avoid complexity.

C. Create one folder per request to keep them separate.

D. Use random folder names to make it creative and fun.

Solution

1. Step 1: Consider project size and teamwork needs

   Large projects benefit from clear structure to avoid confusion and improve collaboration.

2. Step 2: Apply best practice for organization

   Using multiple collections by module and folders inside them groups requests logically, making it easier for teams to find and manage APIs.

3. Final Answer:

   Create multiple collections for different modules and use folders inside each collection to group related requests. -> Option A

4. Quick Check:

   Modular collections + folders = clarity and teamwork [OK]

Hint: Use collections by module and folders inside for clarity [OK]

Common Mistakes:

• Putting all requests in one collection without folders
• Creating one folder per request causing clutter
• Using unclear or random folder names