Projects and settings

Create a QA project, add members, and set up labels, custom fields, lists and the Orchestrator workspace that runs automated tests.

A QA project holds the releases, requirements, test cases, test sets, executions and defects of one product or team. Its key (for example FIN) appears in the web address and cannot be changed. Create a project# You need a role that can create projects, for example QA Test Manager. Open QA Hub ▸ Projects and select New project. Enter a short Key (for example FIN) and a Name, and optionally a Description. Under Access, choose Open to everyone with QA Hub access or Restricted to members. Select Create project. The project's Overview opens. Change general settings# Open Configuration ▸ Project settings ▸ General to change the Name, Description, Owner and Access. Under Key prefixes you can change the prefix of each kind of item (Defect, Execution, Release, Requirement, Test case, Test set). Changing a prefix keeps existing keys. Select Save settings. Under Lifecycle, Archive project makes the project read-only and hides it from the project list (show it again with Show archived projects). Deleting a project deletes everything in it and cannot be undone. Add members# Project settings ▸ Members lists who belongs to the project. Members matter for a project that is Restricted to members: only members see it. Pick a person in Add a member. Select Add. Select Remove to take someone out. Labels# Labels are coloured tags you put on releases, requirements, test cases, test sets, executions and defects, and filter by. Project settings ▸ Labels ▸ New label asks for a Name, a Colour and a Description. Custom fields# Project settings ▸ Custom fields ▸ New custom field adds your own fields to items. Give it a Name, Key, Type (date, date and time, multi select, multiline text, number, single select, text, URL, user or yes/no), the items it Applies to, and optionally a Group, Default value, Required and Options. A field that no item has a value for can be deleted; otherwise Archive it. Lists# Project settings ▸ Lists holds the choices used across the project: Requirement types: epic, feature, user story and so on. Test case categories: regression, smoke, E2E and so on. Environments: where an execution ran (development, test, staging, production). Reports group by it. Edit a value's label, select Add value to add one, tick Archived to retire one, then select Save. Connect the project to Orchestrator# Automated test cases run as jobs in the project's default workspace. The workspace needs: a process that pins a tests package: a project whose output type is tests (each entry point is one test) or a process project whose entry points are marked as test cases. See Packages and processes. a machine with a connected Robot that has the runtime the package needs, and a robot account for unattended jobs. See Machines and robots. Steps: Open Project settings ▸ Automation. Under Default workspace, pick the workspace and select Save. Select Resync catalog. QA Hub reads the packages the workspace's processes pin and lists every test it finds, with its name and automation key (package::entry point). Resync again after you publish a new version of the tests package. A test that disappeared from the package is retired, and test cases linked to it keep a readable link. Frameworks shows the automation providers the project can use. Orchestrator has a Catalog (tests are picked from the list above and run on your Robots). The others (Appium, Cypress, JUnit, NUnit, Playwright, pytest, Robot Framework, Selenium, xUnit, Other framework) support Ingestion: their results are reported to QA Hub from your CI pipeline. See Run tests. Next steps# Releases and requirements Test cases

Create a project

Change general settings

Add members

Labels

Custom fields

Lists

Connect the project to Orchestrator

Next steps