Folder hierarchy in Postman - Framework Patterns

Framework Mode - Folder hierarchy

Folder Structure

Postman-Tests/
├── Collections/
│   ├── UserManagement.postman_collection.json
│   ├── ProductAPI.postman_collection.json
│   └── Auth.postman_collection.json
├── Environments/
│   ├── Development.postman_environment.json
│   ├── Staging.postman_environment.json
│   └── Production.postman_environment.json
├── Globals/
│   └── globals.postman_globals.json
├── Scripts/
│   ├── pre-request-scripts.js
│   └── test-scripts.js
├── Data/
│   ├── user-data.json
│   └── product-data.json
├── Reports/
│   └── test-run-report.html
└── README.md

Test Framework Layers

• Collections: Group of API requests organized by feature or service.
• Environments: Variables for different deployment stages (dev, staging, prod).
• Globals: Variables shared across all collections and environments.
• Scripts: JavaScript files for reusable pre-request and test scripts.
• Data: External JSON files for data-driven testing inputs.
• Reports: Generated test run reports for analysis.

Configuration Patterns

• Environment Files: Use separate environment JSON files to switch API endpoints and credentials easily.
• Global Variables: Store common values like tokens or IDs accessible across collections.
• Data Files: Use external JSON files for parameterizing requests to support data-driven tests.
• Script Reuse: Place common pre-request and test scripts in the Scripts folder and reference them in collections.

Test Reporting and CI/CD Integration

• Use Newman CLI to run Postman collections in CI/CD pipelines.
• Generate HTML or JSON reports from Newman runs and save them in the Reports folder.
• Integrate with Jenkins, GitHub Actions, or GitLab CI to automate test execution on code changes.
• Use environment variables in CI to select target environment dynamically.

Best Practices

• Organize collections by feature or API domain for clarity.
• Keep environment-specific data separate to avoid accidental data leaks.
• Reuse scripts to reduce duplication and ease maintenance.
• Use data files for testing multiple scenarios without changing requests manually.
• Automate test runs with Newman and integrate with CI/CD for continuous feedback.

Self Check

Where would you add a new collection for testing the "Order API" in this folder structure?

Key Result

Organize Postman tests with clear folders for collections, environments, scripts, data, and reports to enable maintainable and scalable API testing.

Practice

1. What is the main purpose of using folders in Postman collections?

easy

A. To create user accounts in Postman

B. To write code for API endpoints

C. To change the API server URL

D. To organize API requests into groups for better management

Solution

1. Step 1: Understand folder usage in Postman

   Folders group related API requests inside a collection to keep things organized.

2. Step 2: Identify the correct purpose

   Folders help manage and run related tests easily by grouping requests logically.

3. Final Answer:

   To organize API requests into groups for better management -> Option D

4. Quick Check:

   Folder purpose = Organize requests [OK]

Hint: Folders group requests logically for easy management [OK]

Common Mistakes:

• Thinking folders are for coding API logic
• Confusing folders with environment settings
• Assuming folders change server URLs

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

easy

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

B. Click 'New' and select 'Environment'

C. Edit the collection and type folder name in URL

D. Drag and drop requests outside the collection

Solution

1. Step 1: Recall Postman UI actions

   To create a folder, you right-click the collection and choose 'Add Folder'.

2. Step 2: Eliminate incorrect options

   Options B, C, and D do not create folders; they relate to environments, editing URLs, or invalid drag actions.

3. Final Answer:

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

4. Quick Check:

   Create folder = Right-click collection + Add Folder [OK]

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

Common Mistakes:

• Choosing environment creation instead of folder
• Trying to create folder by editing URLs
• Dragging requests outside collections

3. Given this folder structure in Postman:

Collection
 ├─ Folder A
 │   ├─ Request 1
 │   └─ Request 2
 └─ Folder B
     └─ Request 3

If you run Folder A, which requests will execute?

medium

A. Request 1 and Request 2

B. Request 1, Request 2, and Request 3

C. Only Request 3

D. No requests will run

Solution

1. Step 1: Understand folder execution scope

   Running a folder executes only the requests inside that folder, not others.

2. Step 2: Identify requests inside Folder A

   Folder A contains Request 1 and Request 2, so only these run.

3. Final Answer:

   Request 1 and Request 2 -> Option A

4. Quick Check:

   Run folder = only its requests [OK]

Hint: Run folder runs only requests inside it [OK]

Common Mistakes:

• Assuming all collection requests run
• Including requests from other folders
• Thinking no requests run when folder runs

4. You created a folder inside a collection but it does not show any requests when you run it. What is the most likely reason?

medium

A. The collection is deleted

B. Postman is offline

C. The folder is empty and has no requests inside

D. You did not save the collection

Solution

1. Step 1: Analyze folder content

   If a folder runs but no requests execute, it likely has no requests inside.

2. Step 2: Check other options

   Collection deletion or Postman offline would cause errors, not empty runs. Not saving collection would prevent folder creation.

3. Final Answer:

   The folder is empty and has no requests inside -> Option C

4. Quick Check:

   Empty folder = no requests run [OK]

Hint: Check if folder contains requests before running [OK]

Common Mistakes:

• Assuming collection deletion causes empty folder run
• Blaming offline status without error
• Forgetting to add requests to folder

5. You want to run tests only for a specific group of related API requests in Postman. How should you organize your collection to achieve this efficiently?

hard

A. Add all requests directly to the collection without folders

B. Create a folder inside the collection and add those requests to it

C. Create multiple collections for each request

D. Use environment variables to filter requests

Solution

1. Step 1: Understand grouping for selective runs

   Folders group related requests so you can run them together easily.

2. Step 2: Evaluate other options

   Multiple collections for each request is inefficient; no folders means no grouping; environment variables do not filter requests.

3. Final Answer:

   Create a folder inside the collection and add those requests to it -> Option B

4. Quick Check:

   Group requests in folder for selective runs [OK]

Hint: Use folders to group and run related requests [OK]

Common Mistakes:

• Creating too many collections for single requests
• Not using folders and running all requests
• Misusing environment variables for request grouping