Recommended workflow

This is the typical path from a new account to completed test execution in Complex QA. Steps marked (optional) can be skipped or done later.

---

Overview

flowchart TD
    A[Register / Login] --> B[Create team]
    B --> C[Invite members]
    C --> D[Create project]
    D --> E[Configure project]
    E --> F[Create test accounts]
    F --> G[Build suite structure]
    G --> H[Create test cases]
    H --> I[Create test run]
    I --> J[Select cases in run]
    J --> K[Use tasks view]
    K --> L[Execute tests]
    L --> M[Review results]

    C -.->|optional| C
    E -.->|optional| E
    F -.->|optional| F
    H -.->|optional| H
    K -.->|optional| K

---

Step-by-step

Step	Action	Details
1	Create a team	Workspace with its own subdomain. You become Administrator. See Teams.
2	Invite users (optional)	Add colleagues who already have accounts. See Team members.
3	Create a project	Container for suites, cases, runs, and accounts. See Projects.
4	Configure the project (optional)	Set name, description, and status (OPEN / CLOSED).
5	Create test accounts (optional)	Store credentials and resources used during testing. Can be added anytime. See Test accounts.
5a	Record execution context (optional)	Project snapshots for browser, OS, URL, and build - for reproducibility. See Execution context.
6	Create test suite structure	Nested suites organize cases in a tree. See Test cases and suites.
7	Create test cases (optional)	Document steps, preconditions, and expected results.
8	Create test cases	Add the cases you plan to execute (same as step 7 when you are ready to run).
9	Create a test run	A run is an execution container for one project. See Test runs.
10	Select tests for the run	On create, pass specific case IDs or use ALL to include every case in the project. You can add more cases later with Add test cases.
11	Use the tasks view (optional)	See work assigned to you: open runs, pending results, and in-progress cases.
12	Perform testing	Set each test run result to Passed, Failed, Skipped, Blocked, or Retest. See Test run results.
12a	File a bug (optional)	On a defect, create a record in the bug tracker: status, priority, reproduction steps.
13	Automated execution report (optional)	Not available yet in the product. Execution is manual through run results.

---

Roles in the workflow

Role	Typical responsibilities
Administrator	Team setup, invites, member roles
Member	Projects, cases, runs, bugs, execution context, execution
Read-only	Browse team data without changing it. See Read-only member role.
Assignee	Any user set on a case, run, or result sees items in Tasks

---

Tables and context menu

Most entity listings and details use data tables. Right-click a row or cell to open the context menu: go to element, clone, delete (where your role allows), and other actions depending on the screen.

Action	How
Copy value	Right-click a data cell → Copy value. The clipboard gets the same text shown in the cell (status label, user name, formatted value). Internal IDs and service columns (checkbox, go-to arrow, sort controls) are not copied.
Bulk actions	Select several rows, then right-click - clone or delete multiple items where enabled.

On pages with tabs (for example Projects or entity details), switching tabs is saved in browser history - use Back / Forward to move between tabs on the same page.

---

Quick links

• First steps - minimal path to your first run
• Entity types - what each object means
• Bug tracker - project defects
• Execution context - environment snapshots
• Limits and access - beta period (2026–2027)

---

Version	1.3.0
Last updated	2026-07-24