Workspace organization in Postman - Test Execution Trace

Test Overview

This test verifies that a user can successfully create a new workspace in Postman and that the workspace appears in the workspace list.

Test Code - Selenium with Python unittest

Postman

import unittest
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

class TestPostmanWorkspaceCreation(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://web.postman.co/')
        self.wait = WebDriverWait(self.driver, 10)
        # Assume user is already logged in for simplicity

    def test_create_workspace(self):
        driver = self.driver
        wait = self.wait

        # Click on workspace dropdown
        workspace_dropdown = wait.until(EC.element_to_be_clickable((By.CSS_SELECTOR, 'button[aria-label="Workspace selector"]')))
        workspace_dropdown.click()

        # Click on 'Create Workspace' button
        create_workspace_btn = wait.until(EC.element_to_be_clickable((By.XPATH, '//button[contains(text(), "Create Workspace")]')))
        create_workspace_btn.click()

        # Enter workspace name
        name_input = wait.until(EC.presence_of_element_located((By.CSS_SELECTOR, 'input[placeholder="Workspace name"]')))
        workspace_name = 'Test Workspace'
        name_input.send_keys(workspace_name)

        # Select workspace type (Personal)
        personal_radio = wait.until(EC.element_to_be_clickable((By.XPATH, '//label[contains(text(), "Personal")]')))
        personal_radio.click()

        # Click 'Create Workspace' confirm button
        confirm_btn = wait.until(EC.element_to_be_clickable((By.XPATH, '//button[contains(text(), "Create Workspace")]')))
        confirm_btn.click()

        # Verify new workspace appears in workspace list
        workspace_dropdown.click()
        workspace_list = wait.until(EC.presence_of_all_elements_located((By.CSS_SELECTOR, 'div[role="list"] div[role="listitem"]')))
        workspace_names = [item.text for item in workspace_list]
        self.assertIn(workspace_name, workspace_names)

    def tearDown(self):
        self.driver.quit()

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

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts and opens Chrome browser to Postman web app	Browser opened at https://web.postman.co/ with login page or main page	—	PASS
2	Clicks on workspace dropdown button to open workspace list	Workspace dropdown menu is visible	—	PASS
3	Clicks on 'Create Workspace' button in dropdown	Create Workspace modal/dialog appears	—	PASS
4	Enters 'Test Workspace' into workspace name input field	Input field contains 'Test Workspace'	—	PASS
5	Selects 'Personal' workspace type radio button	'Personal' option is selected	—	PASS
6	Clicks 'Create Workspace' confirm button	Modal closes, workspace is created	—	PASS
7	Clicks workspace dropdown again to refresh workspace list	Workspace dropdown menu is visible with updated list	Check if 'Test Workspace' is in the workspace list	PASS

Failure Scenario

Failing Condition: The 'Create Workspace' button is not clickable or workspace name input is missing

Execution Trace Quiz - 3 Questions

What is the first action performed after opening the Postman web app?

A Click 'Create Workspace' button

B Click the workspace dropdown button

C Enter workspace name

D Select workspace type

Key Result

Always wait explicitly for UI elements to be present and clickable before interacting to avoid flaky tests.

Practice

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

easy

A. To write code for APIs

B. To organize API tests and related files in one place

C. To deploy APIs to servers

D. To monitor server performance

Solution

1. Step 1: Understand Workspace Function

   A Workspace in Postman is designed to keep API tests and files organized together.

2. Step 2: Eliminate Other Options

   Writing code, deploying APIs, and monitoring servers are not the main functions of a Workspace.

3. Final Answer:

   To organize API tests and related files in one place -> Option B

4. Quick Check:

   Workspace = Organize tests [OK]

Hint: Workspaces group tests and files for easy access [OK]

Common Mistakes:

• Confusing Workspace with API deployment
• Thinking Workspace is for coding APIs
• Assuming Workspace monitors servers

2. Which of the following is the correct way to create a new Workspace in Postman?

easy

A. Go to Settings and click 'Add Workspace'

B. Right-click on a request and choose 'Create Workspace'

C. Drag and drop a collection into the sidebar

D. Click on 'New' button and select 'Workspace'

Solution

1. Step 1: Identify Workspace Creation Method

   In Postman, you create a Workspace by clicking the 'New' button and selecting 'Workspace'.

2. Step 2: Verify Other Options

   Right-clicking requests, using Settings, or drag-and-drop do not create Workspaces.

3. Final Answer:

   Click on 'New' button and select 'Workspace' -> Option D

4. Quick Check:

   Create Workspace = New button [OK]

Hint: Use 'New' button to start creating a Workspace [OK]

Common Mistakes:

• Trying to create Workspace from request right-click
• Looking in Settings for Workspace creation
• Dragging collections to create Workspace

3. Consider you have two Workspaces named 'Team API' and 'Personal API'. You switch from 'Personal API' to 'Team API'. What happens to your collections and environments?

medium

A. You see only collections and environments saved in 'Team API' Workspace

B. All collections and environments from both Workspaces are merged and shown

C. Collections and environments from 'Personal API' remain visible

D. Postman deletes collections from 'Personal API'

Solution

1. Step 1: Understand Workspace Isolation

   Each Workspace in Postman shows only its own collections and environments.

2. Step 2: Analyze Switching Effect

   Switching to 'Team API' hides 'Personal API' collections; no merging or deletion occurs.

3. Final Answer:

   You see only collections and environments saved in 'Team API' Workspace -> Option A

4. Quick Check:

   Workspace switch = show own data only [OK]

Hint: Switching Workspace shows only its own collections [OK]

Common Mistakes:

• Thinking collections merge across Workspaces
• Assuming collections stay visible after switch
• Believing Postman deletes collections on switch

4. You created a Workspace but your team members cannot see it. What is the most likely reason?

medium

A. The Workspace is private and not shared with the team

B. The Workspace name is too long

C. You did not add any collections yet

D. Postman does not support team Workspaces

Solution

1. Step 1: Check Workspace Sharing Settings

   By default, Workspaces can be private; team members cannot see private Workspaces unless shared.

2. Step 2: Evaluate Other Options

   Workspace name length, empty collections, or Postman features do not block visibility.

3. Final Answer:

   The Workspace is private and not shared with the team -> Option A

4. Quick Check:

   Private Workspace = team can't see [OK]

Hint: Share Workspace to let team members access it [OK]

Common Mistakes:

• Assuming name length affects visibility
• Thinking empty collections hide Workspace
• Believing Postman lacks team Workspace support

5. You want to organize your API tests so that your team can collaborate easily and find tests quickly. Which combination of Workspace practices is best?

hard

A. Keep all tests in one Workspace without sharing to avoid confusion

B. Create many private Workspaces with vague names to separate tests

C. Use clear Workspace names, share Workspace with team, and group related collections inside

D. Use Workspace only for personal tests and share collections separately

Solution

1. Step 1: Identify Best Practices for Team Collaboration

   Clear names, sharing Workspaces, and grouping related collections help teamwork and easy finding.

2. Step 2: Reject Poor Practices

   Private vague Workspaces, no sharing, or separating collections outside Workspace reduce collaboration and clarity.

3. Final Answer:

   Use clear Workspace names, share Workspace with team, and group related collections inside -> Option C

4. Quick Check:

   Clear names + share + group = best practice [OK]

Hint: Clear names and sharing improve teamwork [OK]

Common Mistakes:

• Making Workspaces private only
• Using unclear Workspace names
• Avoiding sharing to prevent confusion