Workflows

Workflows let you define the states that test cases, test runs, and test sessions move through during their lifecycle — from "Not Started" to "In Progress" to "Closed". States are configured per context, scoped to projects, and can trigger automatic transitions as work progresses.

What is a workflow state?

A workflow state is a label that represents where a test item currently stands. States help your team answer questions like:

• Which test cases are active and ready to run?
• Is this test run in progress or has it been closed?
• What is the current status of this session?

You define the states that make sense for your team — naming them, choosing an icon and colour, and controlling which projects they appear in. TestOrchestrator has no hardcoded states; every workspace starts from scratch and builds exactly the workflow vocabulary it needs.

Three independent contexts

Workflow states are organised into three contexts, each covering a different type of test item. States in one context are completely separate from the others.

Repository

States for test cases stored in the repository — for example, Active, Draft, Deprecated. Repository states also control which test cases are pulled in when a new test run is created (see Workflow Settings).

Runs

States for test runs — the batches in which test cases are executed. Examples: Planned, In Progress, Closed. Runs states can be configured to transition automatically when execution milestones occur.

Sessions

States for individual test sessions — the units of work within a run. Examples: Open, Active, Completed. Like Runs, Sessions states support automatic transitions.

Getting started

1. Go to Admin → Workflows.
2. Select the context tab you want to configure: Repository, Runs, or Sessions.
3. Click New State to create your first workflow state for that context.
4. Click Settings to configure context-specific behaviour — such as which Repository states are included in new runs, or which state a run transitions to when it is closed.
5. Repeat for each context your team uses.

Who can manage workflows?

The Workflows page is accessible to Tenant Admins and Project Admins.