QMetry Test Management: Complete Guide for QA Teams

QMetry Test Management (QTM) is an enterprise test management platform built for teams already living inside Atlassian's ecosystem. If your project tracking runs on JIRA, QMetry slots in as a native plugin and gives you test case authoring, test cycles, execution tracking, and requirements traceability — all without leaving JIRA.

This guide covers what QMetry actually does, how to set it up, where it shines, and where it falls short.

What QMetry Is (and Who It's For)

QMetry is a test management tool available as a JIRA Cloud app (QTM for JIRA Cloud) and as a standalone server product. The core premise: your requirements live in JIRA, your bugs live in JIRA, so your tests should too.

It targets mid-to-large QA teams — typically organizations with 10+ testers, formal QA processes, compliance requirements, or regulated industries where traceability between requirements and test results is mandatory. If you're a 3-person startup with a CI pipeline, QMetry is almost certainly overkill.

Core Features

Test Case Repository

QMetry organizes test cases into a hierarchical folder structure within each JIRA project. Each test case has:

• Summary and description — plain text or structured steps
• Step-by-step execution instructions — expected vs actual result fields per step
• Custom fields — priority, test type, automation status, component
• Labels and versions — for filtering and reporting

Test cases are versioned. When you update a test case, previous execution results stay linked to the version that was run — critical for audit trails.

Test Cycles and Execution

Test cycles are the execution containers. You create a cycle (e.g., "Sprint 42 Regression"), add test cases to it, assign them to testers, and track execution status: Not Executed, Pass, Fail, WIP, Blocked.

Execution tracking is granular — you can mark individual test steps as pass/fail, attach screenshots, log defects directly from the execution screen, and add comments. Every execution creates an immutable execution record linked to the cycle, tester, and timestamp.

Requirements Traceability

This is where QMetry earns its keep for compliance-heavy teams. You can link JIRA issues (requirements, stories, epics) to test cases. The traceability matrix shows which requirements have test coverage, which tests are passing, and which requirements have open defects — all in one view.

For teams doing ISO, FDA, or SOC 2 audits, this matrix is often a deliverable. Generating it manually from spreadsheets is painful; QMetry makes it a click.

Reporting and Dashboards

QMetry ships with built-in reports: test execution summary, cycle progress, defect distribution, coverage reports. Reports are filterable by sprint, version, component, tester, and custom fields. You can export to PDF or CSV.

The JIRA integration means execution data flows into JIRA dashboards as gadgets — useful for PMs who want test status without logging into a separate tool.

QMetry AI: Automated Test Authoring

QMetry has added AI-assisted test case generation. You provide a user story or requirement text, and the AI generates draft test cases with steps, expected results, and suggested priority. The output is editable and follows your project's custom field schema.

In practice, the AI generation works best for CRUD-style functionality — login flows, form validation, API contracts. Complex business logic or multi-system workflows still need human authoring. Treat it as a drafting assistant, not a replacement for a QA engineer who understands the system.

Real Setup Walkthrough

1. Install QTM for JIRA Cloud Go to the Atlassian Marketplace, search "QMetry Test Management," and install it to your JIRA Cloud instance. Requires JIRA site admin.

2. Enable for a project In your JIRA project settings, enable QMetry. This creates the Test Cases, Test Cycles, and Traceability menu items under your project.

3. Create your test case folder structure Navigate to Test Cases → create folders matching your application modules (e.g., Authentication, Checkout, API). This structure is project-specific and doesn't carry across projects by default.

4. Author test cases Create test cases inside folders. For each case: write the title, add preconditions, break execution into numbered steps with expected results, assign priority and test type.

5. Link to requirements Open a test case, click "Requirements," and link to JIRA issues. One test case can cover multiple requirements; one requirement can have multiple test cases.

6. Create a test cycle Go to Test Cycles → New Cycle. Set a name, start/end dates, version. Add test cases (manually or via filter). Assign test cases to team members.

7. Execute Testers open their assigned test cases, step through each, mark pass/fail, attach evidence, and log defects. Progress updates in real time on the cycle dashboard.

8. Report After execution, pull the Cycle Summary report — overall pass rate, tester breakdown, defect count. Export for stakeholders.

Limitations to Know Before Committing

Cost scales with users. QMetry's JIRA Cloud pricing is per-user per-month. For large teams this adds up fast — check the Atlassian Marketplace for current pricing tiers.

Steep learning curve. The interface is dense. New team members typically need 2-3 hours of onboarding just to understand the cycle/folder/execution hierarchy. Documentation is available but not great.

JIRA dependency. If you move off JIRA, you lose QMetry. All your test cases, execution history, and traceability live inside JIRA's data model.

No native automation execution. QMetry tracks automation status (a test case can be marked "automated") and stores automation keys, but it doesn't run your tests. You need a separate CI system and integration layer.

Reporting is rigid. The built-in reports cover the standard cases. Custom reporting requires Atlassian's reporting tools or data export to BI.

When to Consider an Alternative

QMetry makes sense when: you're already all-in on Atlassian, you have compliance traceability requirements, and you have the budget and team size to justify the complexity.

If you're a smaller team that needs test automation, AI-native test creation, and execution monitoring without building a test management empire — HelpMeTest is worth evaluating. It's usage-based pricing at $0.003/run (no base fee, no per-user fees), runs tests on Robot Framework + Playwright, and includes AI-powered test generation, visual testing, and 24/7 health monitoring. Setup takes minutes, not days.

QMetry is a serious enterprise tool. It does what it promises. The question is whether your team's scale and process maturity justify what it demands in return.