Navigating the QAM Hub Interface
The QAM Hub interface is organized around two levels: your organization at the top, and the projects inside it. Almost all day-to-day testing work happens inside a project, where you will find test cases, runs, requirements, reports, and a dashboard. This guide gives you a quick tour of where everything lives.
Organizations and projects
When you sign in, you are working within an organization — the top-level account that contains everything. Inside it are one or more projects, and each project holds its own test data, fully separated from other projects. Most navigation starts by opening the project you want to work in.
If you have not set these up yet, see creating your organization and first project.
Inside a project
Once you open a project, the left-hand navigation gives you access to the main areas of QAM Hub:
- Test cases & suites — your hierarchical test suites, groups, and individual test cases. This is where test content is created and organized.
- Checklists — lighter, column-based checklist suites for exploratory or release checks.
- Test runs — where you execute test cases and record pass / fail / blocked / skipped results.
- Requirements — requirements imported from manual, Jira, or GitHub sources, linked to test cases for traceability.
- Milestones — release-readiness tracking with due dates and status.
- Automation — upload and review automated test results from Playwright and Cypress.
- Agent flows — autonomous AI-driven test runs and the runners that execute them (if enabled for your project).
- Library — the project's shared store of uploaded images and attachments.
- Reports — coverage, traceability, automation, release-readiness, and other reports, exportable to PDF.
The project dashboard
Each project has a customizable dashboard built from drag-and-drop widgets, so you can arrange the view that matters to you. Available widgets include project overview stats, active milestone readiness, recent test runs, recent automation runs, and team activity over the last 30 days.
Reports
The Reports area gathers the project's analytics in one place, with report types covering test runs, automation, automation coverage, team activity, coverage, traceability, release readiness, AI retrospectives, quality, and defects. Reports can be exported to PDF for sharing. For more detail, see overview of report types.
Your personal settings
Some settings are specific to you rather than the project:
- Profile → AI — configure your personal AI key, used for AI-assisted features.
- Profile → API tokens — generate tokens (used, for example, by the Playwright and Cypress reporters) to push automated results into QAM Hub.
- Favorites — mark items you use often for quick access.
Finding the version and what's new
The current QAM Hub version is shown in the footer. Selecting it opens a "What's New" view with the latest changes, so you can see what has been added or fixed in recent releases.
What you can see depends on your role
Your role determines which areas and actions are available. A viewer sees read-only data, an executor can create and run tests, and project or organization admins see additional settings and management areas. If an option described here is not visible to you, your role may not have access to it.