Test reports · Evidence Available now

The report is your reproduction guide.

Every run retains an HTML report, logs, and replay videos. Failed cases record the browser and step where they stopped, with screenshots, so developers can open the report and follow the same path.

Request a demoExplore the platform

Status: passed · failed · inconclusive · skipped / Severity: critical · major · minor · trivial

Evidence Available now

Preserve the exact moment of failure.

Every failed case automatically saves a screenshot at the stopping point, a step-by-step replay, and execution logs. One report link gives everyone the same evidence to work from.

  • Separate evidence for Chromium, Firefox, and WebKit. Even a failure in just one engine includes that engine's screenshots.
  • Replay videos preserve inputs and click order so developers can follow the same steps.
  • Automatically publish failures as Jira issues, linked in both directions to the results.
  • API test failures record contract violations alongside execution logs.
More about UI testing & UX review

Release decision Available now

Above the results,
one release decision.

At the top of every report is a PASS, CONDITIONAL, or FAIL decision. Without counting passes, see whether the release is ready, who needs to review it, and what is blocking it.

  • FAIL: stable tests fail at critical/major severity, or critical/major repository vulnerabilities remain open.
  • CONDITIONAL: only minor/trivial failures, quarantined or inconclusive tests, or requirements coverage below 80%. A person reviews and decides.
  • PASS: all executed tests pass on the first attempt.
  • Decision rationale is listed item by item, ready for the QA lead to include in the release memo.
Explore all quality assurance features

Coverage Available now

Document what has not been checked, too.

A report with only pass counts hides gaps. Qoretix documents what the run actually checked across requirements, checklist categories, and screens, keeping unvisited screens and unexecuted items visible.

  • Requirements coverage: the share of testable statements extracted from documents supported by actual runs.
  • Checklist coverage: whether each of 17 categories has executed tests.
  • Screen coverage: the share of collected screens actually opened by tests, plus the unopened list.
  • This is not code coverage. A case that has not run does not count as verified.

What each run retains

The files you receive after a run.

All outputs stay with execution history, ready for workspace members to reopen at any time.

  1. HTML report Available now

    One browser-ready document with the decision, status counts, failures by severity, and three coverage measures.

  2. Replay video Available now

    A video of each failed case's screens and inputs, showing the exact click where execution stopped.

  3. Execution log Available now

    A chronological record of steps and results per case. API failures include requests and responses.

  4. Evidence files Available now

    Screenshots and attachments grouped by case. Link them in your issue tracker or download them directly.

  5. Jira issues Available now

    Automatically create Jira issues with failure severity and evidence links. Open the related run from the issue.

  6. Quality trends Available now

    Calculate weekly pass rates, approval times (p50/p95), PR suggestion acceptance, and automation ratios from run history.

Frequently asked questions

Questions about reports and evidence.

How is inconclusive different from failed?
Failed means the actual result differs from the expectation. Inconclusive means a test could not complete, so the result is unknown. It causes CONDITIONAL, not FAIL, and a person investigates to resolve it as passed or failed.
How do quarantined tests appear in reports?
A same-commit flip rate of at least 20% across the last 20 runs triggers quarantine. Tests continue running and reporting but cannot cause FAIL; they support a CONDITIONAL decision. Measurement is per browser engine.
What is included in Jira issues?
The failed case, severity, and a result link with screenshots, replay videos, and logs. Issues and results link to each other, so retest outcomes are visible from Jira. Other issue trackers are in preview.
How does this relate to existing CI test reports?
GitHub Actions triggers Qoretix on pushes and PRs, and reports stay in Qoretix workspaces. Alongside unit test reports, Qoretix adds user-journey and API contract results with a release decision.
Who does what when the decision is CONDITIONAL?
Testers triage minor/trivial failures and quarantined/inconclusive items. QA leads sign off, or customer-role users decide on release. With managed QA, experts handle triage, retesting, and the release memo, leaving the final decision to the customer owner.
Who can view reports, and how long are they retained?
Reports and evidence stay with execution history in the workspace, visible only within the organization. The customer role can view results and decide on release. For retention and data handling terms, see Deployment & data handling.

Let's read your next release report together.

See what your first run report looks like in a demo using your staging environment.

Request a demoTalk about managed QA

sales@qoretix.com+82-33-242-0210Weekdays, 10:00–18:00 KST