Folders

Overview

Folders in Test Orchestration provide a way to organize your workflows and projects into logical groups. This helps teams manage large numbers of workflows, improves discoverability, and makes navigation easier.

---

Why Use Folders?

Organization

Group related workflows together by feature, sprint, test type, or team for better structure and management.

Team Collaboration

Scalability

Permissions

---

Creating a Folder

Step-by-Step

1. Navigate to Projects: Open your project in Test Orchestration

2. Click "New Folder" button

3. Enter Folder Name: Give your folder a descriptive name

4. Choose Parent Folder (optional): Nest folders within other folders

5. Click Create: Your folder is ready to use

Naming Best Practices

Use clear, descriptive names that reflect the folder's purpose:

• ✅ E-Commerce-Checkout

• ✅ API-Integration-Tests

• ✅ Sprint-23-Tests

• ✅ Mobile-Regression

• ❌ Test1, Workflow, Temp

---

Organizing Workflows in Folders

Moving Workflows

1. Select the workflow you want to move

2. Click "Move" or use drag-and-drop

3. Choose destination folder

4. Confirm: Workflow is moved to the new folder

Copy Workflows Between Folders

1. Right-click workflow → Select "Copy"

2. Navigate to destination folder

3. Paste: Creates a copy with "Copy of" prefix

---

Folder Structure Examples

Example 1: By Test Type

📁 Test Orchestration
├── 📁 Web-Tests
│   ├── Login-Workflow
│   ├── Checkout-Workflow
│   └── Registration-Workflow
├── 📁 API-Tests
│   ├── User-API-Tests
│   ├── Payment-API-Tests
│   └── Order-API-Tests
├── 📁 Mobile-Tests
│   ├── iOS-Tests
│   ├── Android-Tests
│   └── Cross-Platform-Tests
└── 📁 Integration-Tests
    ├── E-Commerce-Integration
    └── Payment-Gateway-Integration

Example 2: By Team

📁 Test Orchestration
├── 📁 QA-Team
│   ├── 📁 Sprint-23
│   └── 📁 Regression-Suite
├── 📁 DevOps-Team
│   ├── CI-CD-Workflows
│   └── Smoke-Tests
└── 📁 Platform-Team
    ├── API-Tests
    └── Integration-Tests

Example 3: By Application Area

📁 Test Orchestration
├── 📁 Authentication
│   ├── Login-Flow
│   ├── Registration-Flow
│   └── Password-Reset-Flow
├── 📁 Payments
│   ├── Credit-Card-Validation
│   ├── Payment-Processing
│   └── Refund-Flow
└── 📁 User-Profile
    ├── Profile-Update
    └── Preference-Management

---

Managing Folders

Rename a Folder

1. Right-click folder → Select "Rename"

2. Enter new name

3. Press Enter or click outside to save

Delete a Folder

⚠️ Caution: Deleting a folder will delete all workflows inside it. This action cannot be undone.

To delete safely:

1. Move all workflows out of the folder first

2. Then delete the empty folder

---

Folder Permissions

Setting Access Controls

1. Right-click folder → Select "Settings" or "Permissions"

2. Choose who can access:

   • Private (only you)

   • Team (specific team members)

   • Public (everyone in organization)

3. Set permission level:

   • View only

   • Edit

   • Admin

4. Save settings

Permission Inheritance

Note: Folder permissions apply to all workflows inside that folder. Workflows inherit folder-level permissions unless overridden individually.

---

Best Practices

✅ Do

• Use consistent naming conventions across your folder structure

• Create a clear hierarchy that matches your organizational structure

• Keep folder depth to 3-4 levels maximum for easy navigation

• Review and archive completed test folders periodically

• Document the purpose of folders with descriptions

❌ Don't

• Create too many nested folder levels (avoid deep hierarchies)

• Use vague folder names like "Temp" or "Test"

• Mix different naming conventions in the same project

• Leave unused folders cluttering the workspace

• Store unrelated workflows in the same folder

---

Searching and Filtering

Finding Workflows in Folders

1. Use the Search bar at the top

2. Filter by folder: Click folder name to view only its contents

3. Use breadcrumb navigation: Click folder path to navigate

Quick Navigation

• Expand/Collapse: Click arrow next to folder name

• Favorites: Star important folders for quick access

• Recent: View recently accessed workflows

---

Collaboration with Folders

Team Workflows

1. Create Team Folder: Organize workflows for your team

2. Set Permissions: Allow team members to view/edit

3. Add Description: Document folder's purpose for team

4. Use Comments: Leave notes on workflows for teammates

Example Workflow

Team Lead creates: 📁 Sprint-23-Testing
  ├── Sets Permissions → Team can edit
  ├── Adds Description → "All tests for Sprint 23"
  ├── Creates 📁 Critical-Path
  │   └── Shares with team for review
  └── Creates 📁 Regression-Suite
      └── Team members contribute workflows

---

Troubleshooting

Issue: Can't see all workflows in folder

Solution:

• Check if you have view permissions for the folder

• Verify the workflows haven't been moved to another folder

• Use search to find the workflow

Issue: Folder is taking too long to load

Solution:

• Too many workflows in one folder may slow performance

• Consider splitting workflows into separate folders

• Contact support if performance issues persist

---

Related Topics

• Creating Workflows

• Run Configuration

• Session Persistence

• Troubleshooting