Getting Started with QMetry: From Setup to First Test Cycle

QMetry has a reputation for being powerful but dense. That reputation is earned — there's a lot to configure before you get to the actual testing. This guide cuts the noise and walks you through exactly what you need to do to go from zero to a running test cycle in QMetry for JIRA Cloud.

Prerequisites

Before you start, you need:

• A JIRA Cloud instance (you need to be a site admin to install apps)
• An Atlassian Marketplace account (usually same as your Atlassian account)
• JIRA projects already set up with the features and issues you'll test

QMetry is not a standalone signup — it's installed into an existing JIRA Cloud workspace. If you don't have JIRA, start there first.

Step 1: Install QMetry from the Marketplace

1. Log into your JIRA Cloud instance as a site admin
2. Go to Settings → Apps → Find new apps
3. Search "QMetry Test Management"
4. Click Get app → Try it free (30-day trial is available)
5. Review permissions and confirm installation

After installation, QMetry adds menu items to your JIRA navigation and project sidebars. You'll see "Test Cases," "Test Cycles," and "Reports" under each JIRA project where you enable it.

Licensing: QMetry pricing is per-user, billed through the Atlassian Marketplace monthly alongside your JIRA subscription. Current pricing tiers are on the Marketplace listing — costs scale with your JIRA user count.

Step 2: Enable QMetry on Your Project

QMetry needs to be activated per project.

1. Open your JIRA project
2. Go to Project Settings → QMetry Test Management
3. Click Enable for this project
4. Configure the default fields visible in this project (you can customize later)

Once enabled, the project sidebar shows QMetry sections. Other projects on your JIRA instance don't get QMetry access until you enable it there separately.

Step 3: Configure Custom Fields

Before authoring test cases, configure which custom fields your team needs. Navigate to QMetry Administration → Fields.

Standard fields you should review:

• Test Type (manual, automated, performance) — add values that match your team's terminology
• Priority (critical, high, medium, low) — usually fine as-is
• Automation Status (not automated, in progress, automated) — used to track test automation coverage
• Component — mirrors your JIRA project components; no setup needed if components are already configured

Skip elaborate custom field setups on day one. Add what you're certain you'll use. You can add fields later, but removing fields after test cases have data in them requires migration work.

Step 4: Create Your Test Case Folder Structure

QMetry organizes test cases in folders within each project. Plan this before you start creating test cases — reorganizing later is tedious.

A practical folder structure for a typical web application:

📁 Authentication
   📁 Login
   📁 Registration
   📁 Password Reset
📁 Dashboard
   📁 Navigation
   📁 Widgets
📁 Checkout
   📁 Cart
   📁 Payment
   📁 Order Confirmation
📁 API
   📁 Authentication Endpoints
   📁 Data Endpoints
📁 Regression
   📁 Smoke Tests
   📁 Critical Path

Navigate to Test Cases → + New Folder to create this structure. Folders are project-scoped — you're building this per JIRA project, not globally.

Step 5: Author Your First Test Cases

With folders created, start writing test cases. Navigate into a folder and click + New Test Case.

Required fields:

• Summary — the test case name. Be specific: "User can log in with valid email and password" not "Login test"
• Status — Draft, Ready for Review, Approved (use Draft until the team reviews it)
• Priority — High/Medium/Low

Steps tab: Add test steps. Each step has:

• Description — what the tester does ("Click the 'Sign In' button")
• Expected Result — what should happen ("User is redirected to /dashboard and sees their name in the header")

Write steps at the level of granularity that matches your tester's familiarity. For new testers: more detail. For experienced testers who know the product: higher-level steps are fine.

Example test case (Login — valid credentials):

Step 1: Navigate to https://app.example.com/login
Expected: Login page loads, email and password fields visible

Step 2: Enter valid email in email field
Expected: Email field accepts input

Step 3: Enter correct password in password field
Expected: Password field accepts input (characters masked)

Step 4: Click "Sign In" button
Expected: Loading indicator appears briefly

Step 5: Verify redirect to dashboard
Expected: URL changes to /dashboard, user's first name appears in top navigation

Link to requirements: After saving the test case, go to the Requirements tab and link to the JIRA story or issue this test covers. This is what powers the traceability matrix later.

Step 6: Create a Test Cycle

A test cycle is a planned execution run. Navigate to Test Cycles → + New Cycle.

Cycle configuration:

• Name — "Sprint 12 Regression" or "v2.4 Release Testing" — be specific
• Start Date / End Date — the testing window
• Environment — staging, production, etc.
• Version — link to a JIRA version/release if applicable

Adding test cases to the cycle: After creating the cycle, click Add Test Cases. You can:

• Browse folders and select individually
• Filter by label, component, priority, or test type
• Add all tests in a folder at once

For a first cycle, add a small set — 10-20 test cases — to learn the execution flow before loading up hundreds.

Assigning to testers: Select test cases in the cycle and click Assign. Assign to team members (must be JIRA users in your project). Testers see their assigned cases in the QMetry dashboard.

Step 7: Execute the Test Cycle

Have a tester open the cycle and start execution.

1. Navigate to Test Cycles → [your cycle] → [tester's assigned cases]
2. Click a test case to open execution view
3. Work through each step, marking Pass or Fail per step
4. If a step fails: add a comment describing what went wrong, attach a screenshot
5. At the bottom, mark the overall execution status (Pass/Fail/Blocked/WIP)
6. If logging a defect: click Create Defect — this opens a pre-filled JIRA issue creation dialog

The cycle dashboard updates in real time as testers submit executions. You can see progress without asking testers to report status.

Step 8: Review Results and Generate a Report

After executions complete (or mid-cycle for progress checks):

1. Go to Reports → Cycle Summary
2. Select your cycle
3. Review: total test cases, pass count, fail count, blocked, not executed
4. For defect breakdown: Reports → Defect Distribution
5. For requirement coverage: Reports → Traceability Matrix

Export to PDF or CSV for stakeholder distribution.

Common First-Week Mistakes

Creating test cases without a folder structure first. Moving test cases between folders after the fact works, but if you have 100 cases in the wrong place it's tedious. Plan first.

Skipping requirement links. The traceability matrix is one of QMetry's strongest features. If you don't link test cases to requirements from the start, you'll have to backfill this manually.

Adding all team members as testers immediately. Start with a small group who learn the tool well, then expand. QMetry's interface is not intuitive — guided onboarding for new testers saves support overhead.

Creating giant test cycles. A cycle with 500 test cases assigned to one sprint is overwhelming. Break cycles by feature area or risk level. Run smoke cycles (20-30 critical tests) separately from full regression.

Realistic Time Expectations

• Install and enable QMetry: 15-30 minutes
• Configure custom fields and folder structure: 1-2 hours
• Author your first 50 test cases: 4-8 hours (plan for 5-10 minutes per case)
• First test cycle setup and execution: 1-2 hours for planning; execution time depends on your test cases

Budget a week of part-time setup before QMetry is running smoothly for a team. This is not a "sign up and start testing in 10 minutes" tool.

If You Want Faster Time-to-Value

If your team's immediate need is automated test coverage rather than manual test management, HelpMeTest takes a different approach: you describe tests in plain language, the AI generates Robot Framework + Playwright automation, and tests run on a schedule with 24/7 monitoring. No installation into JIRA, no folder structure planning, no cycle configuration.

It's $100/month flat (no per-user fees), and you can run your first automated test in under 15 minutes. The trade-off: no formal manual test case repository or JIRA-native traceability — different tool, different use case.

QMetry is worth the setup investment if formal test management and traceability are requirements. Just go in knowing what you're signing up for.