Collections and folders in Postman

Introduction

Collections and folders help you organize your API tests in Postman. They keep your tests neat and easy to find.

You want to group related API requests together for a project.

You need to run a set of tests in a specific order.

You want to share a group of API tests with your team.

You want to separate tests by feature or module.

You want to save and reuse tests later.

Syntax

Postman

Collection {
  Folder {
    Request1
    Request2
  }
  Request3
}

A Collection is a container for folders and requests.

A Folder groups related requests inside a collection.

Examples

This example shows a collection named 'User API' with two folders: 'Login' and 'Profile'. Each folder has requests related to that feature.

Postman

Collection: User API
  Folder: Login
    Request: POST /login
  Folder: Profile
    Request: GET /profile

A collection with requests directly inside it, without folders. Good for small sets of tests.

Postman

Collection: Shopping Cart
  Request: GET /cart
  Request: POST /cart/add

Sample Program

This is a simple setup in Postman where you create a collection and folder, add requests, and run them to test your API.

Postman

// Create a collection named 'Todo API'
// Add a folder named 'Tasks'
// Add two requests inside 'Tasks' folder

// Request 1: GET /tasks
// Request 2: POST /tasks

// Run the collection to test the API endpoints

Important Notes

Use descriptive names for collections and folders to find tests easily.

You can export collections to share with others or import collections shared by teammates.

Folders help run a subset of requests inside a collection.

Summary

Collections group your API tests in Postman.

Folders organize requests inside collections.

Use them to keep tests clear, reusable, and shareable.

Practice

1. What is the main purpose of a Collection in Postman?

easy

A. To create user accounts in Postman

B. To store environment variables

C. To write JavaScript code for tests

D. To group API requests and tests together for better organization

Solution

1. Step 1: Understand what a Collection is

   A Collection in Postman is used to group API requests and tests logically.

2. Step 2: Differentiate from other features

   Environment variables and user accounts are separate features, not Collections.

3. Final Answer:

   To group API requests and tests together for better organization -> Option D

4. Quick Check:

   Collection = Group API requests [OK]

Hint: Collections group requests; folders organize inside collections [OK]

Common Mistakes:

• Confusing collections with environments
• Thinking collections store user data
• Mixing collections with test scripts

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

easy

A. Drag and drop requests outside the collection

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

C. Click 'New' and select 'Environment'

D. Use the 'Runner' tab to create folders

Solution

1. Step 1: Identify folder creation method

   Folders are created by right-clicking a collection and choosing 'Add Folder'.

2. Step 2: Eliminate incorrect options

   Creating environments or using Runner does not create folders.

3. Final Answer:

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

4. Quick Check:

   Create folder = Right-click collection [OK]

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

Common Mistakes:

• Trying to create folders from the Runner tab
• Confusing environments with folders
• Dragging requests outside collections

3. Given a collection with two folders named Users and Orders, which statement is true about running tests in Postman?

medium

A. You can run all requests in the collection or just one folder at a time

B. You must run each request individually; folders cannot be run

C. Folders run automatically when you open the collection

D. Running a folder deletes all requests inside it

Solution

1. Step 1: Understand running collections and folders

   Postman allows running all requests in a collection or just those inside a specific folder.

2. Step 2: Verify incorrect options

   Folders do not run automatically, and running does not delete requests.

3. Final Answer:

   You can run all requests in the collection or just one folder at a time -> Option A

4. Quick Check:

   Run collection or folder = possible [OK]

Hint: Run entire collection or single folder as needed [OK]

Common Mistakes:

• Believing folders run automatically
• Thinking folders cannot be run
• Confusing running with deleting requests

4. You created a folder inside a collection but it does not appear in the sidebar. What is the most likely cause?

medium

A. The folder was not saved properly after creation

B. Postman does not support folders inside collections

C. You need to restart Postman to see new folders

D. Folders only appear after running the collection

Solution

1. Step 1: Check folder creation process

   If a folder does not appear, it is often because it was not saved or confirmed properly.

2. Step 2: Exclude other causes

   Postman supports folders, no restart needed, and folders appear immediately, not after running.

3. Final Answer:

   The folder was not saved properly after creation -> Option A

4. Quick Check:

   Unsaved folder = not visible [OK]

Hint: Always save folder after creating to see it [OK]

Common Mistakes:

• Assuming Postman lacks folder support
• Restarting Postman unnecessarily
• Expecting folders to appear only after running

5. You want to organize a large API test suite in Postman with multiple related requests. Which approach best uses collections and folders for clarity and reusability?

hard

A. Create one folder per API and put all requests directly inside it without collections

B. Put all requests in a single collection without folders to avoid complexity

C. Create one collection per API, then use folders inside it to group related requests by feature

D. Create separate collections for each request to isolate tests

Solution

1. Step 1: Understand best organization practice

   Using one collection per API keeps tests grouped logically, and folders inside help organize by feature.

2. Step 2: Evaluate other options

   Folders cannot exist without collections, too many collections reduce reusability, and no folders cause clutter.

3. Final Answer:

   Create one collection per API, then use folders inside it to group related requests by feature -> Option C

4. Quick Check:

   Collection + folders = best organization [OK]

Hint: Use collections for APIs, folders for features inside [OK]

Common Mistakes:

• Trying to create folders without collections
• Overusing collections for each request
• Avoiding folders causing messy tests