Folder hierarchy in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a folder hierarchy in Postman?

A folder hierarchy in Postman is a way to organize your API requests into folders and subfolders. It helps keep your tests and requests neat and easy to find, just like organizing files in folders on your computer.

beginner

Why should you use folders in Postman collections?

Folders help group related API requests together. This makes it easier to run tests for a specific part of your API and keeps your workspace clean and manageable.

intermediate

How do subfolders improve folder hierarchy in Postman?

Subfolders allow you to create layers of organization. For example, you can have a folder for 'User APIs' and inside it subfolders for 'Login', 'Profile', and 'Settings'. This helps find requests faster and understand the API structure better.

beginner

Can you run tests on a whole folder in Postman?

Yes! You can run all requests inside a folder or subfolder at once. This is useful to test a group of related API endpoints together, saving time and ensuring consistency.

beginner

What is a best practice for naming folders in Postman?

Use clear and descriptive names that reflect the API functionality inside. For example, use 'Authentication', 'User Management', or 'Payments' instead of vague names like 'Folder1'. This helps everyone understand the folder contents quickly.

What is the main purpose of using folders in Postman?

A To increase API response speed

B To organize API requests logically

C To change API request methods

D To delete API requests automatically

Folders help organize API requests logically, making them easier to manage and run.

Can you create subfolders inside folders in Postman?

A Yes, to create multiple levels of organization

B No, only one level of folders is allowed

C Only if you use a paid version

D Subfolders are automatically created by Postman

Postman allows creating subfolders inside folders to organize requests in multiple levels.

What happens when you run a folder in Postman?

A Only the first request in the folder runs

B The folder is deleted after running

C Postman exports the folder as a file

D All requests inside the folder run in order

Running a folder executes all requests inside it sequentially.

Which naming style is best for Postman folders?

A Single letters

B Random numbers

C Clear descriptive names related to API features

D Names with special characters only

Clear descriptive names help understand folder contents quickly.

How does folder hierarchy help in API testing?

A It helps group and run related tests easily

B It changes API endpoints automatically

C It hides API requests from users

D It slows down test execution

Folder hierarchy groups related tests, making it easier to run and manage them.

Explain how folder hierarchy in Postman helps organize API requests and testing.

Think about how you organize files on your computer.

Describe best practices for creating and naming folders in Postman collections.

Imagine explaining your folder setup to a teammate.

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