Sign in
Full comparison

Everything Qmatrix does — and how it stacks up.

The complete feature list, grouped by where it fits in the software testing lifecycle, next to what a typical legacy QA tool (TestRail, Zephyr, or a shared spreadsheet) gives you. No asterisks, no “Enterprise-tier only” fine print.

QmatrixTypical legacy QA tool

Requirements & traceability

Requirements management First-class requirements with priority, status, and JIRA/Confluence links Often a separate tool or a spreadsheet tab
Requirements-to-test traceability Live coverage matrix — every requirement shows its linked cases, runs, and defects Manual cross-referencing
Coverage gaps surfaced automatically

Test design

Test cases as structured objects Steps, expected results, priority, type — not rows in a tab Rows in a sheet, or rigid ticket fields
Unlimited folder/suite tree Tenant-wide shared hierarchy, any depth, drag-and-drop reorganization Flat lists or shallow folders
Custom fields on cases Higher tiers only, commonly
Version control & approvals on test cases Maker-checker design review with diff/redline between iterations Enterprise-tier only, if at all
BDD / Gherkin authoring
AI test-case drafting Draft cases from a requirement or a GitHub/Jira issue Capped or unavailable

Test execution

Test plans Scoped to environment and milestone, with rollup progress
Real-time collaborative runs See who is testing what, live, as results come in
Step-level results & evidence Per-step pass/fail with attachments on the run Case-level only, commonly
Scheduled / recurring runs Add-on or unavailable
Configurable status workflows Per-tenant custom statuses and transitions, enforced server-side Fixed statuses

Defects

Native defect tracking Defects are first-class — not “every test is a Jira issue” Bounced to an external tracker
Two-way defect ↔ run sync A resolved bug and a passing retest are never two separate stories
SLA, escalation, watchers, @mentions Varies
Sync to GitHub / GitLab / Linear / Jira Native, no Jira subscription required Jira-centric

Milestones, releases & change

Milestones with rollup progress Varies
Releases & release-readiness view Rare
Change requests & sprints

Reporting & dashboards

Executive / KPI dashboard Executed, passed, failed, open defects, coverage — real-time Static exports, commonly
Coverage, pass-rate & defect reports
Real-time, no manual refresh

Integrations & migration

GitHub / GitLab / Linear native Built for teams that don't live in Jira
Jira & Confluence Jira-native only, usually
TestRail / CSV import Fidelity report before import, idempotent re-runs, 14-day rollback Export hell reported by users
Outbound webhooks Signed and replay-safe (run completed, defect created) Varies
CI service-account tokens Long-lived PATs for pipelines, not an 8-hour user session Varies

Collaboration

Real-time presence
Comments on cases, requirements & plans Defect-only, commonly
Saved filters per user, per screen Varies
Command palette & natural-language search

Security & compliance

Tenant isolation at the data layer Enforced in the data-access layer, not per-endpoint Often UI-only
Tamper-evident audit log SHA-256 hash-chained, verifiable — per-project and tenant-level Basic log or none
SSO / audit log Team tier ($13/user) Enterprise-tier only ($74/seat)
GDPR export, anonymize & true hard-delete Soft-delete only, commonly
Lapsed billing goes read-only, never deletes data Varies

Pricing model

Priced per active tester $5/user — not per Jira seat or per whole company $37+/seat, or priced on your Jira estate
Free tier that fits a real team 5 users, 2 projects, 500 cases — no card Trial only, or none
Migration never paywalled Import is included on every plan, including Free Gated or manual

See it against your current tool, in your own data.

Start free — 5 users, 2 projects, no card — and import your TestRail or CSV suite in an afternoon.