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.