For uat

User acceptance testing fails on the reporting step, not on the testing step.

The people doing UAT are the ones who know the business process. They are also, almost always, the people least equipped to write a bug report your engineers can act on — and the least likely to have a licence for the tool your engineers live in.
Start freeNo credit card required.

The situation

What this usually looks like

  • The test script comes back as a spreadsheet

    Column D says "failed". Column E says "did not work as expected". There is no browser, no screenshot, no URL and no way to reproduce it without booking a call with the tester.

  • Business users have no tracker licence

    Buying Jira seats for twenty people who will file four issues each is not a defensible cost, so the reports route through a coordinator and lose detail at every hop.

  • Environment differences dominate

    Half of UAT findings turn out to be a browser version, a corporate proxy or a screen width nobody on the team uses. None of that is in the spreadsheet.

  • Sign-off is blocked by ambiguity

    You cannot close a UAT cycle on findings you cannot reproduce, so the cycle extends while people try to remember what they clicked two weeks ago.

Why this fits

What changes for uat

Testers report from inside the application
The button is on the screen where the test failed. No licence, no account, no separate portal — which is what makes it realistic for twenty business users rather than two coordinators.
The environment is captured for you
Browser and version, operating system, window and screen size, pixel density, time zone and page load time, on every bug report, automatically. Most environment-related findings resolve themselves at triage.
The steps are recorded, not remembered
Up to fifty actions — clicks with their visible labels, form submissions and page changes — so a report describes the path through the process rather than the tester recollection of it.
Findings move through explicit statuses
Pending, planned, in progress, shipped, rejected. Marking one shipped emails the tester who raised it, which is how a UAT cycle closes without a status meeting.

Who this is not for

Save yourself the trial

This is not test case management. If you need to define scripts, assign them, and track coverage and pass rates against requirements, you need a UAT platform such as TestRail or Xray — this only makes the reporting half of the cycle work. The comparison pages say which tool we would send you to instead.

FAQ

Questions

Do UAT testers need a licence or an account?
No. They report from inside the application under test, with no login of their own and nothing to install. That is what makes it workable for a group of business users rather than a small coordinator team.
Does it manage test cases or scripts?
No. It captures findings, not coverage. Keep your test scripts wherever they live today and use this for the part where a tester needs to tell you that step seven failed and why.
Can we host UAT and production separately?
Yes. Give the UAT environment its own project, key, inbox and domain allowlist so acceptance findings never mix with live customer reports. Projects are unlimited on the plan.

Put it on your site today.

One script tag. Unlimited projects, widgets and reports on one plan, and your users never make an account.

Start freeRead the docs