Collections and folders in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Postman Collection Structure

Which statement best describes the relationship between collections and folders in Postman?

A Folders are used to group requests inside a collection to organize them logically.

B Collections are subsets inside folders to separate different API endpoints.

C Folders exist outside collections and cannot be part of any collection.

D Folders and collections are the same and can be used interchangeably.

💡 Hint

Think about how you organize files on your computer into folders inside a main folder.

In Postman, a collection is a container for API requests. Folders help organize these requests inside the collection logically.

❓ Predict Output

intermediate

Output of Folder Count in a Collection

Given a Postman collection JSON with 3 folders, what will be the output of the following test script counting folders?

Postman

const folderCount = pm.collection.folders.count();
console.log(folderCount);

A 0

B undefined

C 3

D Error: pm.collection.folders is not a function

💡 Hint

pm.collection.folders.count() returns the number of folders in the current collection.

The count() method on pm.collection.folders returns the total number of folders in the collection, which is 3 here.

❓ assertion

advanced

Correct Assertion for Folder Existence

Which assertion correctly verifies that a folder named 'User APIs' exists in the current Postman collection?

Postman

const folderNames = pm.collection.folders.all().map(folder => folder.name);

A pm.test('Folder exists', () => pm.expect(folderNames).to.equal('User APIs'));

B pm.test('Folder exists', () => pm.expect(folderNames).to.include('User APIs'));

C pm.test('Folder exists', () => pm.expect(folderNames).to.have.property('User APIs'));

D pm.test('Folder exists', () => pm.expect(folderNames).to.be.true);

💡 Hint

Check if an array includes a specific string.

Using to.include checks if the array contains the folder name 'User APIs'. Other options are incorrect because they expect exact equality or wrong property checks.

🔧 Debug

advanced

Debugging Folder Access Error

Why does this Postman test script throw an error: TypeError: pm.collection.folders.map is not a function?

Postman

const folderNames = pm.collection.folders.all().map(folder => folder.name);
pm.test('Check folders', () => pm.expect(folderNames.length).to.be.above(0));

A pm.collection.folders is undefined because the collection has no folders.

B The map function is misspelled and should be maps().

C The test script is missing a required import for map function.

D pm.collection.folders is an object, not an array, so map() is not available.

💡 Hint

Check the data type of pm.collection.folders before using array methods.

pm.collection.folders is a FolderList object, not a plain array. It does not support map() directly. You need to convert it to an array first using all() method.

❓ framework

expert

Best Practice for Organizing Large API Tests in Postman

For a large API project with hundreds of requests, which approach best uses Postman collections and folders to maintain test clarity and reusability?

A Create one collection with folders grouping requests by resource type, and use folder-level pre-request and test scripts for shared setup and assertions.

B Create separate collections for each API endpoint without folders to keep things simple.

C Put all requests in a single folder inside one collection and duplicate pre-request scripts in each request.

D Avoid using folders; instead, use environment variables to separate requests logically.

💡 Hint

Think about grouping related requests and sharing setup code efficiently.

Using folders inside a collection to group related requests allows better organization. Folder-level scripts help reuse setup and assertions, improving maintainability.