Skip to content
Quorum
Start free trial

Quorum Reporter

Coming soon

Stop paying for
another test tool.

Repository, step-by-step runs, plans, coverage per Jira story and AI-drafted bugs your QA approves, for $12 per tester a month. You pay for the people who test, not for everyone on your Jira site.

Get notifiedCalculate your savings

Coming soon: not on sale yet, so there is no trial or checkout. “Get notified” emails support@usequorum.dev.

ReporterRepositoryRunsPlansMilestonesReports
Checkout / Discount codes
KeyTitleLast result
  • PAY-C10Apply a valid percentage codePassed
  • PAY-C11Apply an expired code at checkoutPassed
  • PAY-C12Apply a code typed in lowercaseFailed
  • PAY-C13Discount larger than the order totalBlocked
  • PAY-C14Reject a malformed codeUntested
PAY-C12Version 3

Apply a code typed in lowercase

EdgeMedium
  1. 1Add a product to the cart and open checkoutExpected: The total is $80.00
  2. 2Enter the code save10 in lowercaseExpected: 10% is taken off the total
  3. 3Place the orderExpected: The receipt shows the discount

Linked stories

PAY-123Apply a discount code at checkout

History

  1. v3Expected result of step 2 edited2 days ago
  2. v2Step 3 addedlast week
  3. v1Created from Designerlast week

Savings calculator

Do the math.
With your numbers.

Pick the tool you pay for and your team size. Every figure is computed from what you enter and the vendor’s published list price, with the source linked.

Your team today

Everyone who writes or runs test cases. Reporter is priced per tester.

Billing period

A year for 8 testers

  • Qase$3,360

  • Quorum ReporterComing soon$960

    $120 per tester a year

You keep

$2,400a year

That is $200 a month back in your budget, at list prices.

Get notified

Reporter is coming soon. “Get notified” opens an email to us; no mailing list.

  • $35 per user a month, billed yearly.
  • US dollars, before taxes. List prices as of October 2026; they can change, so check their site. Source: qase.io/pricing (opens in a new tab).
  • A price comparison, not a feature one: other tools do things Reporter’s first version does not, such as importing cases or CI results, custom fields and shared steps.

Runs and bugs

Run it step by step.
Review the bug.

Record passed, failed, blocked or skipped for every case and every step, with a note. When a step fails, the AI drafts the Jira bug from the case, the step and your note. Nothing reaches Jira until you accept it.

Release 2.4 · Checkout
6 passed · 1 failed · 1 blocked · 4 untested
PAY-C12 · version 3Failed

Apply a code typed in lowercase

  1. 1

    Add a product to the cart and open checkout

    Expected: The order total is $80.00

    Passed
  2. 2

    Enter the code save10 in lowercase

    Expected: The code is accepted and 10% is taken off

    Failed

    Actual: “Code not recognized”. SAVE10 in capitals works.

  3. 3

    Place the order

    Expected: The receipt shows the discount

    Untested
Bug draftDrafted by AI

Title

Lowercase discount codes are rejected at checkout

Steps to reproduce

  1. Add a product to the cart and open checkout
  2. Enter the code save10

Expected

10% off the total

Actual

“Code not recognized”

Linked to PAY-123. Nothing is created until you accept.

EditCreate bug in Jira

How it works

From story
to sign-off.

The release flow your team already follows, in one place next to Jira. The AI helps at one step, and even there a person signs off.

  1. 01You

    Bring the cases in

    Write them in the repository, or let Designer send the cases your QA accepted, already linked to their story.

  2. 02You

    Organize

    Folders, a new version on every save, and links to the Jira stories each case covers.

  3. 03You

    Plan the release

    Keep the cases you run every release in a plan, and group plans and runs under a milestone with a date.

  4. 04You

    Run

    Start a run from folders, a selection or a plan. It pins each case’s version; record a result for every step.

  5. 05AI drafts, you decide

    File the bug

    From a failed step, the AI drafts the Jira bug. You edit and accept it; only then is it created and linked.

  6. 06Reporter keeps it up to date

    Report

    Run progress, pass rate over time and the latest result of every case linked to each story.

Features

The test tool,
minus the bloat.

The parts of test management your team uses every release, connected to Jira and next to the AI that designed the cases.

Coverage by storyRelease 2.4
  • PAY-123Apply a discount code at checkoutAt risk
    5 cases
  • PAY-118Save a card for laterPassing
    4 cases
  • PAY-127Pay with a bank transferIn progress
    4 cases
  • PAY-131Gift cards at checkoutNo cases
    0 cases

  • A repository with history

    Folders, cases with steps and expected results, and a new version on every save. Read the history and restore any version.

  • Linked to the story

    Link a case to one or more Jira stories. The story gets a link back to the case, without a Jira issue per case.

  • Manual runs, step by step

    Passed, failed, blocked or skipped for each case and each step, with notes. Results are never overwritten; every one stays in the history.

  • Plans and milestones

    Plans hold the cases you run every release; milestones group plans and runs toward a date.

  • Reports and story coverage

    Run progress, pass rate over time, and the latest result of every case linked to a story, so you see which stories are at risk.

  • Bugs drafted by AI, created by you

    Title, steps to reproduce, expected and actual result, drafted from the failed step. You edit and accept it before anything is created.

Switch from Qase, TestRail or Xray

Switch at the next release.
Not over a weekend.

There is no automatic import yet, and we will not pretend there is. This is how the move works, and we will plan it with you if you want a hand.

  1. 01

    Start with the next release

    Open a Reporter project for it. Your current tool keeps its history; you simply stop adding to it.

  2. 02

    Bring the cases you still run

    New cases arrive from Designer once your QA accepts them, already in a folder and linked to their story. Regression cases you still need, you recreate in Reporter’s editor: title, preconditions, steps, expected results.

  3. 03

    Run the release in Reporter

    Plans, step-by-step results, AI-drafted bugs and coverage per story from the first run. Keep the old tool read-only until nobody opens it, then cancel it.

Want a hand-held migration?

Tell us which tool you use and how many cases you still run. We plan the move with you, folder by folder.

Talk to us

What you keep

  • A repository of cases in folders, with versions
  • Manual runs with a result for every step
  • Plans and milestones toward a release
  • Reports on progress, pass rate and coverage per story
  • Cases linked to their Jira stories

What gets better

  • Priced per tester, not per user of your Jira site
  • Cases arrive from Designer already linked to their story, with nothing copied by hand
  • Bugs drafted by AI from the failed step, created in Jira only after you accept them
  • One plan, one price: no tier to outgrow
  • No Marketplace app: it connects to Jira Cloud with an API token

Not in Reporter yet

  • Automatic import from other tools
  • Importing automated results from CI
  • Custom fields and shared steps
  • Attachments on results

If your team depends on one of these today, keep your current tool for now. Designer sends to it as well.

Side by side, with sources: Quorum vs Qase, Quorum vs TestRail, Quorum vs Xray, Quorum vs Zephyr. All comparisons.

Pricing

One plan.
Per tester.

Pay for the people who test, not for everyone on your Jira site. Everyone gets the same Reporter, and a licence works in every workspace its owner is a member of.

Compare it with your current tool

Reporter

Coming soon

$12per user a month

Or $120 per user a year. US dollars, before taxes.

  • A repository of test cases in folders, with every version kept
  • Cases linked to Jira stories, with a link back on the story
  • Manual runs with a result for every step
  • Plans and milestones to organize runs toward a release
  • Reports: run progress, pass rate and coverage per story
  • Jira bugs drafted by AI from a failed result, created only after you review them
  • A shared workspace for your team, with owners and members

Not on sale yet. The free trial opens when Reporter launches.

FAQ

Questions about Reporter.

When can we use Reporter?
Reporter is not on sale yet. Its price is already set, and you can start it from the pricing page the day it launches. To hear when that is, write to support@usequorum.dev.
Do we need Designer to use Reporter?
No. Reporter is sold on its own: write your cases by hand, organize them, run them and file bugs. With Designer, accepted cases arrive in a Reporter folder already linked to their story, so nothing is copied by hand.
Does the AI create bugs in Jira on its own?
Never. From a failed result, the AI drafts the bug from the case, the failed step, your note and the story. You edit the draft and accept it; only then is the Bug created in the story’s Jira project and linked to the story. If no draft can be produced, you write the bug yourself.
How do cases connect to Jira?
A case can be linked to one or more Jira stories, and each link puts a link on the story that points back to the case. No Jira issue is created per case, so your backlog stays clean. Coverage per story shows the latest result of every case linked to it.
Can we import our cases from Qase, TestRail or Xray?
Not automatically yet. Start Reporter with your next release: Designer sends new cases straight into a Reporter folder, and you recreate the regression cases you still run. Keep your current tool read-only for its history. For a hand-held migration, write to support@usequorum.dev and we plan the move with you.
Who can see our cases and runs?
Reporter data belongs to a workspace. Owners invite members by email; members see and work on the workspace’s cases, runs, plans and reports. Designer sessions and tool connections stay personal: each member uses their own Jira token.
How is Reporter priced?
$12 per user a month, or $120 a year. A licence belongs to a person and works in every workspace they are a member of. For a team, or for invoicing, talk to us from the pricing page. See pricing

Also from Quorum: Quorum Designer

Let Designer write the cases.

Paste a Jira key and Designer drafts the test suite, asks about the rules the story leaves open, and sends the cases your QA accepts straight into a Reporter folder.

Explore Designer

Reporter is coming soon.

Designer is available today and sends to the test tool you already use, so you can start now and move the runs over when Reporter launches.

Try Designer free for 7 daysGet notified