Knowledge Base

Getting Started

• Signing Up and Starting Your Trial

  Create a QAM Hub workspace in minutes: no card, no plan to pick, a 30-day Advanced trial with every feature, and a plan chosen at the end.

• Creating Your Organization and First Project

  Step-by-step guide to setting up your organization and first project in QAM Hub, the containers that hold all your suites, test cases, and runs.

• Understanding Roles and Permissions

  Learn the role tiers in QAM Hub — organization admin and member, plus project admin, user, and viewer — and what each level can access.

• Inviting and Managing Users

  Step-by-step guide to inviting team members to your QAM Hub organization, assigning project roles, and managing access including Google SSO.

• Navigating the QAM Hub Interface

  A quick tour of the QAM Hub interface: how organizations and projects are structured and where to find test cases, runs, reports, and your settings.

• Importing from TestRail

  Move suites, test cases, custom fields, milestones and run history from TestRail into QAM Hub. What you need, what transfers, and what does not.

• Importing from Qase

  Move Qase projects into QAM Hub with an API token: suites, cases, custom fields, milestones and run results with history. What transfers and what to check.

• Exploring the Sample Project

  Create a pre-filled Sample Project with realistic test cases, runs, checklists and automation results, and learn QAM Hub without touching real data.

Test Cases & Suites

• Creating Test Suites and Test Cases

  Learn how to organize tests into suites and groups and create structured test cases with steps, expected results, tags, and attachments in QAM Hub.

• Using Custom Fields

  How to create custom fields in QAM Hub to capture structured data on test cases — priority, type, component, or any attribute your team needs to track.

• Working with Steps and Expected Results

  How to write clear test steps and expected results in QAM Hub, attach images to each block, and keep your test cases repeatable and easy to follow.

• Test Case Templates

  How to create reusable test case templates in QAM Hub that pre-fill title, steps, expected results, and custom fields so new cases start consistent.

• Tags and Test Organization

  How QAM Hub organizes tests with suites and groups, and how tags add a flexible layer to slice your test inventory across that structure.

• Version History and Rollback

  How QAM Hub automatically versions every test case, what each snapshot captures, and how to roll back to an earlier version without losing history.

• Importing & Exporting Test Cases via CSV

  How to bulk-import test cases into QAM Hub from CSV and export them back out — for migrating from spreadsheets or another tool, and for backups.

Test Runs & Execution

• Running Tests and Recording Results

  Step-by-step guide to creating test runs, assigning testers, recording pass/fail/blocked/skipped results, and tracking execution history in QAM Hub.

• Execution Statuses Explained

  Pass, fail, blocked, skip, and untested in QAM Hub: what each status means, when to use it, and how status choices change your run and coverage reports.

• Assigning Testers to a Run

  How to assign testers to test cases within a run in QAM Hub so each person knows what they own and run progress is easy to track.

Automation

• Uploading Playwright Reports

  How to get Playwright results into QAM Hub — upload the JSON report in the UI or push automatically from CI with the official reporter.

• Uploading Cypress Reports

  How to get Cypress results into QAM Hub via the Mochawesome report — upload it in the UI or submit automatically from CI, with manual-case linking.

• Automation Coverage Reporting

  How to read automation coverage and health in QAM Hub — pass rate, flakiness, stability, trends, and which manual cases your automation covers.

• Uploading JUnit XML Reports with the CLI (Selenium, Robot Framework, WDIO and others)

  Send JUnit XML from Selenium, WebdriverIO, pytest, TestNG, Robot Framework and other runners to QAM Hub with one CLI command, locally or from your CI job.

AI Features

• Generating Test Cases with AI

  Generate test cases and checklists in QAM Hub from a description or screenshot, review each proposal before it saves, and write inputs that produce usable output.

Account & Security

• Plans, Seats and What Each Plan Includes

  Three per-seat plans compared: what Start covers, what Standard and Advanced add, how paid and free viewer seats work, and how long automation media is kept.

• Billing, Subscriptions and Seat Changes

  How to subscribe, switch between Standard and Advanced, change seats, update the card and find invoices in QAM Hub billing, handled via Stripe.

• What Happens When Your Trial Ends

  When your trial ends, your data stays and test cases can still be exported. How to reopen the workspace and pick Start, Standard or Advanced.

Checklists

• Creating and Running Checklists

  Build checklist suites for release sign-off, smoke passes and exploratory sessions, then run them with one column per browser or tester, from the keyboard.

Integrations

• Connecting an AI Agent over MCP

  Connect Claude Code, Claude Desktop, Cursor or VS Code to QAM Hub over MCP: create an API token, copy the config, and manage cases and runs from your editor.

• Connecting an Issue Tracker

  Connect Jira, GitHub Issues, GitLab, Linear, Asana, Redmine or Trello to QAM Hub: file bugs from failed tests, follow ticket status and sync requirements.

• Connecting Jira

  Connect Jira to QAM Hub with an API token: file bugs from test runs with Jira's required fields, sync requirements from any Jira project, publish coverage back.

• Connecting GitHub Issues

  Connect a GitHub repository's Issues to QAM Hub with a personal access token: file bugs from test runs, track their status, import issues as requirements.

• Connecting GitLab

  Connect GitLab.com or self-hosted GitLab to QAM Hub with an access token: file bugs from test runs, preset milestone or weight, import issues as requirements.

• Connecting Linear

  Connect a Linear team to QAM Hub with a personal API key: file bugs from failed tests with mapped priority, follow status and import issues as requirements.

• Connecting Asana

  Connect an Asana project to QAM Hub with a personal access token: file bugs from failed tests as tasks with tags and custom fields, sync tasks as requirements.

• Connecting Redmine

  Connect self-hosted Redmine to QAM Hub with an API access key: file bugs from failed tests with mapped priority, target version and custom fields, sync issues.

• Connecting Trello

  Connect a Trello board to QAM Hub with an API key and token: file bugs from failed tests as cards in the list you choose, track when they are done, sync cards.