Folder hierarchy in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Folder Hierarchy in Postman Collections

In Postman, how does organizing requests into folders within a collection help in test management?

A It automatically runs all requests in parallel regardless of folder structure.

B It groups related requests together, making tests easier to find and run in batches.

C It encrypts the requests inside folders for security.

D It prevents requests inside folders from being exported.

💡 Hint

Think about how grouping helps in organizing and running tests.

Folders in Postman collections help testers organize related requests. This makes it easier to manage, run, and maintain tests logically grouped by feature or functionality.

❓ Predict Output

intermediate

Output of Running Folder in Postman Collection

Given a Postman collection with two folders: Login with 3 requests and Profile with 2 requests, what is the total number of requests run when you execute the Profile folder?

A 5

B 3

C 2

D 0

💡 Hint

Only requests inside the selected folder run.

Running a folder executes only the requests inside that folder. The Profile folder has 2 requests, so only those 2 run.

❓ locator

advanced

Best Locator for a Folder in Postman Collection JSON

In the exported Postman collection JSON, which key best identifies a folder containing requests?

A "item" key with an array of requests or subfolders

B "info" key with collection metadata

C "event" key with test scripts

D "auth" key with authentication details

💡 Hint

Folders contain requests or other folders inside an array.

The "item" key holds an array of requests or nested folders, representing the folder's contents in the collection JSON.

❓ assertion

advanced

Assertion on Folder Request Count in Postman Tests

You want to write a test script to assert that a folder named Orders contains exactly 4 requests. Which assertion is correct in Postman test scripts?

Postman

const ordersFolder = pm.collection.items.find(item => item.name === 'Orders');
const requestCount = ordersFolder ? ordersFolder.items.length : 0;
// Which assertion below is correct?

A pm.test('Orders folder has 4 requests', () => pm.expect(requestCount).to.eql(4));

B pm.test('Orders folder has 4 requests', () => pm.expect(requestCount).to.be.lessThan(4));

C pm.test('Orders folder has 4 requests', () => pm.expect(requestCount).to.be.greaterThan(4));

D pm.test('Orders folder has 4 requests', () => pm.expect(requestCount).to.be.undefined);

💡 Hint

Check for exact equality of the count.

The assertion checks that the request count equals 4 exactly, which matches the requirement.

🔧 Debug

expert

Debugging Folder Execution Order in Postman Runner

You have a collection with folders A and B. Folder A has 2 requests, Folder B has 3 requests. You run the entire collection in Postman Runner. You notice requests from Folder B run before Folder A. What is the most likely cause?

A Requests inside folders run before folders themselves, causing B to run first.

B Folders are executed in alphabetical order by default, so Folder A runs before B.

C Postman Runner runs folders randomly each time to balance load.

D Folders run in the order they appear in the collection JSON, so Folder B is listed before Folder A.

💡 Hint

Check the order of folders in the collection export JSON.

Postman Runner executes folders in the order they appear in the collection JSON file. If Folder B is listed before Folder A, its requests run first.

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