Folder hierarchy in Postman - Test Execution Trace

Test Overview

This test checks that the Postman collection folder hierarchy is correctly structured. It verifies that the main folder contains the expected subfolders and requests.

Test Code - unittest

Postman

import unittest
from postman_collection import Collection

class TestFolderHierarchy(unittest.TestCase):
    def setUp(self):
        # Load the Postman collection JSON file
        with open('collection.json', 'r') as file:
            self.collection = Collection(file.read())

    def test_main_folder_contains_subfolders(self):
        main_folders = [item for item in self.collection.items if item.name == 'Main Folder']
        self.assertTrue(main_folders, 'Main Folder not found')
        main_folder = main_folders[0]
        subfolder_names = [item.name for item in main_folder.items]
        expected_subfolders = ['Subfolder A', 'Subfolder B']
        for folder in expected_subfolders:
            self.assertIn(folder, subfolder_names, f'{folder} not found in Main Folder')

    def test_subfolder_contains_requests(self):
        main_folder = next(item for item in self.collection.items if item.name == 'Main Folder')
        subfolder_a = next(item for item in main_folder.items if item.name == 'Subfolder A')
        request_names = [item.name for item in subfolder_a.items if hasattr(item, 'request')]
        expected_requests = ['Get User', 'Create User']
        for req in expected_requests:
            self.assertIn(req, request_names, f'Request {req} not found in Subfolder A')

if __name__ == '__main__':
    unittest.main()

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner initialized, collection.json file loaded	—	PASS
2	Find 'Main Folder' in collection items	Collection parsed, folders and requests loaded	Assert 'Main Folder' exists	PASS
3	Check 'Main Folder' contains 'Subfolder A' and 'Subfolder B'	'Main Folder' items listed	Assert 'Subfolder A' and 'Subfolder B' are present	PASS
4	Find 'Subfolder A' inside 'Main Folder'	'Subfolder A' items loaded	—	PASS
5	Check 'Subfolder A' contains requests 'Get User' and 'Create User'	Requests inside 'Subfolder A' listed	Assert 'Get User' and 'Create User' requests exist	PASS
6	Test ends	All assertions passed	—	PASS

Failure Scenario

Failing Condition: Expected folder or request is missing in the collection hierarchy

Execution Trace Quiz - 3 Questions

What does the test verify first in the Postman collection?

A That all requests have valid URLs

B That the 'Main Folder' exists in the collection

C That the collection has no duplicate requests

D That the collection runs successfully

Key Result

Always verify the folder and request structure in your Postman collections to ensure tests target the correct elements and avoid false failures.

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