Runs and verdicts

Know exactly what passed,
what failed, and where.

Run a defined set of scenarios across selected environments and browsers. See each result in one place, with the context needed to investigate failures.

See Qarmiq in action All features
The real thing

A grid you can read in a glance.

One row for each check and one column for each browser. Click a failed cell and a defect opens with the run, device and browser already attached.

  • A run keeps the exact wording it tested, even if the scenario changes later
  • An automation view shows, for every check, whether a person, a script, the AI agent or an external tool verifies it
  • Failed and blocked cells open a defect with the context already attached

Where it stands. Today a person starts every run. Starting one from CI, a push, a pull request or a schedule is on the roadmap.

Release 2.4 smoke runStaging · Desktop · macOS · locked
CheckChromeSafari
Accepts a valid card and confirms the orderverified by a script
passedpassed
Rejects an expired card with a clear messageverified by a person
passedfailed
Never charges twice on a double-clickverified by the agent · defect raised
failedfailed
Locks the form after five failed attemptsverified by a person
blockedblocked
Applies a discount code only onceverified by a script
skippedskipped

Illustrative example.

In practice

What it does.

01

One run. A clear view of every check.

Each run records the scenarios tested, the environment, the browser, and the result for each check. See where behavior held and where it didn’t.

02

Every result has a source.

See whether a person, an automated script, an AI agent, or an external verifier produced each verdict.

03

Turn a failure into an investigation.

Open a failed or blocked result to create a defect with the run context attached, helping your team understand what happened without reconstructing the session from scratch.

Why a run is frozen

The wording tested is the wording kept.

A run is a record of one deliberate pass, so what it checked cannot shift underneath it.

Frozen checks

The checks under your chosen scenarios are frozen when the run is created. Checks added later never appear in it.

Locked once started

A run locks when it has its first result. You can still change verdicts and add another browser.

Who verified it

Every verdict says whether a person, a script, the AI agent or an external tool produced it.

Where it fits

It works with the rest.

Witness

Make every manual test more useful.

A small widget in your own app. Testers test as they normally do, record pass or fail and file defects in place, while Witness keeps the evidence of everything they do.

See Witness → Autonomous testing

Let AI investigate. Make every verdict earn your trust.

Choose Test autonomously on one check or a whole run and an AI agent tests it in a real browser. A separate AI judge decides pass, fail or inconclusive from the evidence.

See Autonomous testing → Defects and briefs

Every bug should come with a clear next step.

Defects carry severity, status, duplicates and attachments, linked to the scenario, check and run where they were found. An AI developer brief turns the captured evidence into something an engineer or a coding agent can act on.

See Defects and briefs →

See a product run from start to finish.

We will set up a project, write the promises that matter and start a first run with you.

See Qarmiq in action All features

Qarmiq is not self-serve yet, so we set each team up directly. Pricing is one flat price per project.