QA Hub overview

What QA Hub is, how its projects, requirements, test cases, test sets, executions and defects fit together, and which roles you need.

BetaQA Hub is in beta. A platform administrator enables it for each tenant, and it must be part of the tenant's subscription. See Platform administration. QA Hub is the quality-management product inside the Orchestrator web app. Use it to plan what has to be tested, describe how to test it, run the tests by hand or on Robots, and follow failures through to fixed defects. Everything lives in a QA project. Open QA Hub# Sign in to Orchestrator. Open the app launcher (top left) and select QA Hub. Pick a project in the Projects list, or switch projects with the project selector at the top of the sidebar. QA Hub reopens the last project you used. How the pieces fit together# Item Key What it is Project for example FIN The container for everything below, with its own members, labels, custom fields, lists and automation settings. Release REL-1 A version or milestone you test for, with dates and a status. Requirement REQ-1 Something the automation must do. Test cases verify requirements. Test case TC-1 How to test something: Manual (steps for a person), Automated (linked to an automated test) or Hybrid. Every change creates a new version. Test set TS-1 A group of test cases you run together: a fixed list (Static) or a rule (Dynamic). Execution EX-1 One run of a test set or of selected test cases, with one result per test case. Defect DEF-1 A problem found by testing, linked to results, test cases and requirements. Automated test cases run as Orchestrator jobs on your Robots. Results from other frameworks (pytest, Playwright, JUnit and others) and from Studio can be reported into QA Hub as well. See Run tests. The sidebar# Inside a project the sidebar has these groups: Project ▸ Overview: counts, coverage, pass rate, release quality, trends and coverage gaps. Planning ▸ Releases, Requirements. See Releases and requirements. Testing ▸ Test cases, Test sets, Executions. See Test cases, Test sets and Run tests. Quality ▸ Coverage, Defects, Reports. See Coverage, Defects and Reports. Configuration ▸ Project settings. See Projects and settings. Every list has Search, Filters and Export CSV, and opens an item when you select its row. Items have Attachments and History tabs. Roles# QA Hub has its own built-in tenant roles. An administrator assigns them under Manage access (see Manage access). Role What it can do QA Hub Administrator Everything in QA Hub, including creating, configuring and deleting projects. QA Test Manager Create and configure projects; manage releases, requirements, test cases, test sets, executions and defects. QA Test Lead Maintain releases, requirements, test cases, test sets and defects; run executions. QA Automation Engineer Write test cases and link them to automated tests, build test sets, run executions, raise defects. QA Manual Tester Write manual test cases, build test sets, record results, raise defects. QA Developer Read everything; edit defects (for example the ones assigned to them). QA Viewer Read everything. A project can be Restricted to members; then only its members see it, whatever their role. Automated tests also need workspace accessBrowsing and resyncing the catalog of automated tests needs read access to the project's default workspace in Orchestrator (for example Automation User there). See Projects and settings. Pickers that list people (owner, assignee, Add a member) read the tenant's user list, which needs permission to view users. If a picker shows no names, ask an administrator to add the person or to assign a role that can view users. Next steps# Create a project Run tests

Open QA Hub

How the pieces fit together

The sidebar

Roles

Next steps