Collections and folders in Postman - Framework Patterns

Framework Mode - Collections and folders

Folder Structure of a Postman Test Project

Postman Workspace
├── Collections
│   ├── User Management
│   │   ├── Login Folder
│   │   │   ├── Login Request
│   │   │   └── Logout Request
│   │   └── Profile Folder
│   │       ├── Get Profile Request
│   │       └── Update Profile Request
│   └── Product Management
│       ├── List Products Folder
│       │   ├── Get All Products Request
│       │   └── Get Product By ID Request
│       └── Create Product Folder
│           └── Create New Product Request
├── Environments
│   ├── Development Environment
│   ├── Staging Environment
│   └── Production Environment
└── Globals
    └── Global Variables

Test Framework Layers in Postman Collections

• Collections Layer: Groups related API requests together. Each collection represents a feature or module.
• Folders Layer: Organizes requests inside collections into smaller groups for better clarity and management.
• Requests Layer: Individual API calls with method, URL, headers, body, and tests.
• Environment Layer: Stores variables like base URLs, tokens, or credentials for different deployment stages.
• Scripts Layer: Pre-request and test scripts to set up data or validate responses.
• Globals Layer: Variables accessible across all collections and environments.

Configuration Patterns in Postman Collections

• Environment Variables: Define variables per environment (e.g., dev, staging, prod) to switch URLs and credentials easily.
• Global Variables: Use for values shared across all environments, like common headers or tokens.
• Collection Variables: Variables scoped to a collection for modularity.
• Secure Storage: Use Postman's built-in secret storage for sensitive data like passwords or API keys.
• Data Files: Use CSV or JSON files for data-driven testing with the Collection Runner.

Test Reporting and CI/CD Integration

• Postman Test Results: View pass/fail status of tests in the Postman app after running collections.
• Newman CLI: Run Postman collections from command line and generate reports in formats like HTML, JSON, or JUnit.
• CI/CD Integration: Integrate Newman runs into pipelines (Jenkins, GitHub Actions, GitLab CI) to automate tests on code changes.
• Report Sharing: Share generated reports with the team for quick feedback.
• Monitoring: Use Postman monitors to schedule automated runs and get alerts on failures.

Best Practices for Postman Collections and Folders

• Organize by Feature: Group requests in collections and folders by related features or API endpoints for clarity.
• Use Variables Wisely: Use environment, collection, and global variables to avoid hardcoding values and ease maintenance.
• Write Clear Test Scripts: Keep test scripts simple and focused on validating response status, body, and headers.
• Keep Sensitive Data Secure: Never hardcode secrets; use environment variables and Postman's secret storage.
• Use Descriptive Names: Name collections, folders, and requests clearly to make navigation easy for all team members.

Self Check Question

Where would you add a new folder for "Order Management" API requests in this Postman framework structure?

Key Result

Organize Postman tests using collections and folders to group related API requests clearly and manage variables per environment.

Practice

1. What is the main purpose of a Collection in Postman?

easy

A. To create user accounts in Postman

B. To store environment variables

C. To write JavaScript code for tests

D. To group API requests and tests together for better organization

Solution

1. Step 1: Understand what a Collection is

   A Collection in Postman is used to group API requests and tests logically.

2. Step 2: Differentiate from other features

   Environment variables and user accounts are separate features, not Collections.

3. Final Answer:

   To group API requests and tests together for better organization -> Option D

4. Quick Check:

   Collection = Group API requests [OK]

Hint: Collections group requests; folders organize inside collections [OK]

Common Mistakes:

• Confusing collections with environments
• Thinking collections store user data
• Mixing collections with test scripts

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

easy

A. Drag and drop requests outside the collection

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

C. Click 'New' and select 'Environment'

D. Use the 'Runner' tab to create folders

Solution

1. Step 1: Identify folder creation method

   Folders are created by right-clicking a collection and choosing 'Add Folder'.

2. Step 2: Eliminate incorrect options

   Creating environments or using Runner does not create folders.

3. Final Answer:

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

4. Quick Check:

   Create folder = Right-click collection [OK]

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

Common Mistakes:

• Trying to create folders from the Runner tab
• Confusing environments with folders
• Dragging requests outside collections

3. Given a collection with two folders named Users and Orders, which statement is true about running tests in Postman?

medium

A. You can run all requests in the collection or just one folder at a time

B. You must run each request individually; folders cannot be run

C. Folders run automatically when you open the collection

D. Running a folder deletes all requests inside it

Solution

1. Step 1: Understand running collections and folders

   Postman allows running all requests in a collection or just those inside a specific folder.

2. Step 2: Verify incorrect options

   Folders do not run automatically, and running does not delete requests.

3. Final Answer:

   You can run all requests in the collection or just one folder at a time -> Option A

4. Quick Check:

   Run collection or folder = possible [OK]

Hint: Run entire collection or single folder as needed [OK]

Common Mistakes:

• Believing folders run automatically
• Thinking folders cannot be run
• Confusing running with deleting requests

4. You created a folder inside a collection but it does not appear in the sidebar. What is the most likely cause?

medium

A. The folder was not saved properly after creation

B. Postman does not support folders inside collections

C. You need to restart Postman to see new folders

D. Folders only appear after running the collection

Solution

1. Step 1: Check folder creation process

   If a folder does not appear, it is often because it was not saved or confirmed properly.

2. Step 2: Exclude other causes

   Postman supports folders, no restart needed, and folders appear immediately, not after running.

3. Final Answer:

   The folder was not saved properly after creation -> Option A

4. Quick Check:

   Unsaved folder = not visible [OK]

Hint: Always save folder after creating to see it [OK]

Common Mistakes:

• Assuming Postman lacks folder support
• Restarting Postman unnecessarily
• Expecting folders to appear only after running

5. You want to organize a large API test suite in Postman with multiple related requests. Which approach best uses collections and folders for clarity and reusability?

hard

A. Create one folder per API and put all requests directly inside it without collections

B. Put all requests in a single collection without folders to avoid complexity

C. Create one collection per API, then use folders inside it to group related requests by feature

D. Create separate collections for each request to isolate tests

Solution

1. Step 1: Understand best organization practice

   Using one collection per API keeps tests grouped logically, and folders inside help organize by feature.

2. Step 2: Evaluate other options

   Folders cannot exist without collections, too many collections reduce reusability, and no folders cause clutter.

3. Final Answer:

   Create one collection per API, then use folders inside it to group related requests by feature -> Option C

4. Quick Check:

   Collection + folders = best organization [OK]

Hint: Use collections for APIs, folders for features inside [OK]

Common Mistakes:

• Trying to create folders without collections
• Overusing collections for each request
• Avoiding folders causing messy tests