Projects

Overview

A Project is the top-level organizational container in Test Orchestration. It serves as the workspace where you create, manage, and execute workflows. Each project can contain multiple workflows, configurations, and environments specific to your testing needs.

circle-info

💡 Think of it this way:

A Project is like a dedicated testing suite for a specific application, module, or feature set. Everything related to that application is contained within that project.


What is a Project?

A Project in Test Orchestration is:

  • A logical container for all testing work related to a specific application or feature

  • An isolation boundary - Projects don't interfere with each other

  • A configuration hub - Project-level settings apply to all workflows within it

  • A collaboration space - Team members can work on the same project

Project Structure

Project (e.g., "E-Commerce Application")
├── Workflows
│   ├── User Registration Flow
│   ├── Payment Processing
│   └── Order Fulfillment
├── Environments
│   ├── Development
│   ├── Staging
│   └── Production
├── Shared Resources
│   ├── Test Data
│   ├── Variables
│   └── Credentials
└── Settings & Permissions
    ├── Access Control
    ├── Notifications
    └── Integrations

Creating a Project

Step-by-Step Guide

  1. Navigate to Projects

    • Click on "Projects" in the main navigation

    • Select "Create New Project"

  2. Enter Project Details

    • Project Name - Give it a descriptive name (e.g., "Mobile Banking App Testing")

    • Description - Brief overview of what this project covers

    • Project Type - Select based on your testing needs:

      • Web Application Testing

      • Mobile Application Testing

      • API Testing

      • Desktop Application Testing

      • Multi-Protocol (combination of above)

  3. Configure Project Settings

    • Default Environment - Set which environment is used by default

    • Time Zone - Select your project's time zone for scheduled executions

    • Notification Recipients - Add email addresses for test alerts

  4. Set Access Permissions

    • Choose who can access this project

    • Set permission levels (Admin, Editor, Viewer)

  5. Complete Setup

    • Click "Create Project"

    • Your project is now ready for workflow creation


Project Management

Renaming a Project

To rename an existing project:

  1. Open the project

  2. Click on Project Settings (gear icon)

  3. Select General

  4. Update the Project Name

  5. Click Save

Archiving a Project

To archive a project (keeping it but hiding from active list):

  1. Open Project Settings

  2. Select Advanced

  3. Click Archive This Project

  4. Confirm the action

Note: Archived projects can be restored from the archive section.

Deleting a Project

To permanently delete a project:

  1. Open Project Settings

  2. Select Advanced

  3. Click Delete This Project

  4. Type the project name to confirm

  5. Click Delete

triangle-exclamation

Project Settings

General Settings

Setting
Purpose
Example

Project Name

Identifier for your project

"E-Commerce Platform"

Description

Brief overview

"Testing suite for order management"

Owner

Primary project owner

Time Zone

For scheduled executions

America/New_York

Permissions & Access

Control who can access and modify your project:

  • Admin - Full access, can manage settings and permissions

  • Editor - Can create and edit workflows, view results

  • Viewer - Read-only access, can view workflows and results

  • Contributor - Can edit workflows but not project settings

Notifications

Configure where execution alerts are sent:

  • Email Recipients - Team members who receive notifications

  • Notification Events - Choose when to notify:

    • Workflow execution started

    • Workflow execution completed

    • Workflow execution failed

    • Scheduled runs missed

Integrations

Link your project to external systems:

  • CI/CD Pipeline - Integrate with Jenkins, GitHub Actions, etc.

  • Issue Tracking - Connect to Jira, Azure DevOps

  • Communication - Slack, Teams for notifications

  • Cloud Storage - AWS S3, Azure Blob for reports


Working with Multiple Projects

Best Practices

  1. Organize by Application

    • One project per application or major feature

    • Example: "Website", "Mobile App", "Backend API"

  2. Separate by Environment

    • While environments exist within projects, consider dedicated projects for isolated testing

    • Example: "E-Commerce Staging", "E-Commerce Production"

  3. Use Descriptive Names

    • Include application name and type

    • Example: "Banking App - Android Mobile"

  4. Document Project Purpose

    • Write clear descriptions

    • Helps team members find the right project

Project Templates

Test Orchestration provides pre-configured project templates to jumpstart your work:

  • E-Commerce Testing - Common workflows for online stores

  • SaaS Application - Multi-tenant app testing patterns

  • Mobile App - Cross-device testing setup

  • API Testing - API-first application patterns

  • Microservices - Multi-service orchestration

To use a template:

  1. Click "Create New Project"

  2. Select "Use a Template"

  3. Choose your template

  4. Customize settings

  5. Click "Create"

circle-info

💡 Pro Tip: Using a template is the fastest way to get started. Templates come with pre-configured workflows and best practices built in.


Project Workflows

Viewing All Workflows

  1. Open your project

  2. Click Workflows tab

  3. See list of all workflows with:

    • Workflow name and description

    • Last executed date

    • Execution status

    • Number of test nodes

Filtering & Searching

  • Search by Name - Type workflow name

  • Filter by Status - Active, Archived, Draft

  • Filter by Tags - Workflows tagged with specific labels

  • Sort Options - By name, date modified, execution frequency


Project-Level Variables

Define variables once at the project level and use them across all workflows:

Creating Project Variables

  1. Open Project Settings

  2. Select Variables

  3. Click Add Variable

  4. Configure:

    • Variable Name - BASE_URL, API_KEY, etc.

    • Variable Type - Text, Number, Boolean, Secret

    • Default Value - Can be overridden in workflows

    • Scope - Available to all workflows in this project

Using Project Variables

In any workflow within the project, reference variables using:

Example:


Sharing & Collaboration

Sharing with Team Members

  1. Open Project Settings

  2. Select Access & Permissions

  3. Click Add Team Member

  4. Enter email and select permission level

  5. Click Invite

Project Collaboration Features

  • Activity Log - See who made what changes and when

  • Comments - Leave notes on workflows

  • Change History - Track modifications to workflows

  • Approval Workflow - Optional workflow approvals before execution


Project Maintenance

Backing Up a Project

To export your project configuration:

  1. Open Project Settings

  2. Select Export

  3. Choose:

    • Export workflows only

    • Export with test data

    • Export with execution history

  4. Click Download

Importing a Project

To import a previously backed-up project:

  1. Click Projects

  2. Select Import Project

  3. Upload the exported file

  4. Configure import options

  5. Click Import


Summary

  • Projects are the organizational foundation of Test Orchestration

  • Multiple projects can run independently without interference

  • Project settings apply to all workflows within the project

  • Permissions and access are managed at the project level

  • Team collaboration is built into projects


Next: Learn how to create and manage Workflows within your project.

Last updated