Witness

Make every manual
test more useful.

Witness captures the actions and application responses during a tester’s session, giving developers a clearer record of what happened when a check passed or failed.

See Qarmiq in action All features
The real thing

A tester, a bar, and a timeline.

Witness stays inert until a run opens your app with a token, then it sits beside the page and records what happens.

  • Records clicks, field interactions, network calls, console and JavaScript errors and performance
  • Never records typed values, and it is not video
  • Reads the tester’s real browser, operating system and device, and warns when they differ from the run

Where it stands. Witness records testers testing, in test sessions. It does not watch real end users.

staging.yourapp.com/checkout
Pay now
A paid order always produces an invoice.
Clicked “Pay now”
POST /api/orders returned 500
Console error: invoice is undefined

Illustrative example. Typed values are never recorded.

In practice

What it does.

01

Test the product as you normally do.

Your testers work in the real application. They record pass or fail while Witness captures relevant interaction events, network activity, console errors, and performance information.

02

Give developers evidence, not a vague bug report.

A timeline of actions and application responses helps explain where a workflow went wrong and gives developers a more useful starting point for investigation.

03

Capture useful context while respecting typed data.

Witness records test sessions, not real end-user activity. Typed values are not recorded, and secrets are removed before stored evidence is retained.

Why it records meaning, not video

Evidence a developer can use, and nothing they should not see.

Witness captures what a tester did and what the app did in reply, in a form that can be read, searched and handed to an agent.

Semantic, not pixels

Interactions, network calls and errors are captured as events, so they can be filtered and read instead of scrubbed through.

Typed values never leave the page

What a tester types is not recorded, and secrets such as tokens, email addresses and card numbers are removed before anything is stored.

A timeline by page

A manual test log groups everything a tester did by page, with failing requests and console errors highlighted.

Where it fits

It works with the rest.

Runs and verdicts

Know exactly what passed, what failed, and where.

A run tests a fixed set of scenarios on one environment, across several browsers, and records pass, fail, blocked or skipped for each check. It keeps the exact wording it tested.

See Runs and verdicts → 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 → 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 →

See what a manual test can tell you.

We add the script tag, open a run and show you what a manual session leaves behind.

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.