SnagRelay
Start free
QA and PM teamsUAT testingCoding agentsDesigners and visual QAReact NativeWordPressChrome extensionIntegrationsPricingDocsGuidesBlogCompareSign in

UAT · User acceptance testing

Testers point.
The ticket explains.

Business testers click Report on the staging site, point at what is wrong and write what they expected. The element, the errors and the steps are attached for them.

Nothing for them to install, and no DevTools. The report lands in your tracker, ready for a developer or their agent.

Start freeOr use the Chrome extension
Michaela
“We cut our ‘cannot reproduce’ rate by 80%.”
Michaela, QA Engineer, Shed Collective
  • Free plan, no card
  • Testers install nothing
  • Works on staging

Example report

UAT

Invoice total is wrong

Pointed at
Invoice › Total (£)
Tester wrote
“Shows 0.00. Should be 1,240.00”
Console
TypeError: Cannot read properties of undefined
Request
GET /api/invoices/118 → 500
Steps
Login › Invoices › Open #118
Browser
Edge 141 · Windows · 1440 px

Sent to your tracker. The tester is emailed when it is fixed.

Jira Linear GitHub GitLab Trello Azure DevOps Jira Linear GitHub GitLab Trello Azure DevOps Jira Linear GitHub GitLab Trello Azure DevOps Jira Linear GitHub GitLab Trello Azure DevOps

The gap

“The total is wrong.” Which invoice, which request, which browser?

  • Business testers

    know what the system should do. They do not know how to write a defect.

  • Developers

    get “the total is wrong”, then spend a day asking which account, which browser, which request.

  • Release owners

    wait for the answers while the acceptance window closes.

How it works

Set it up once. Testers point. The ticket is ready.

  1. 01

    Make a project for the UAT environment

    One project per environment or cycle, for example “UAT round 2”. Reports from it stay apart from your other testing.

  2. 02

    Give testers a button, or an extension

    Add one script tag to the staging site, or turn on the Chrome extension for that project and list the URLs. The site itself does not change.

  3. 03

    Testers point and describe

    They click Report, point at the wrong number and write what they expected. The technical side is captured for them.

What each report carries

A defect a developer can start on.

  • What they pointed at

    The element, named in the words of the page, not a CSS guess.

  • What they saw

    An annotated screenshot, or a screen recording. Hide anything private before sending.

  • What the browser said

    Console errors with file and line, and the requests that failed, with their bodies.

  • What they did

    The steps and page changes before the report, from the session replay.

  • Where and on what

    URL, browser, OS and window width.

  • Who hears back

    When the ticket is marked resolved, the tester who reported it gets an email, and can retest.

Widget or extension

Pick how testers get the button.

You can use either on a project, one at a time. Choose by who owns the environment.

The widget
One script tag on staging. Anyone who can open the site can report, with nothing to install or sign in to.
The Chrome extension
No change to the site. Invited testers sign in by email. How it works

Why trust it

What a QA team saw after switching.

We switched from Usersnap primarily to cut costs, but were also impressed with the quality of the reports and level of detail the platform provides our devs.
Michaela
Michaela
QA Engineer, Shed Collective
We run our own UAT through SnagRelay. Every bug arrives reproducible. Clean releases out.
Igor
Igor
Founder and developer
@igoryussupov
The customisable widget fits perfectly with our brand, and the automatic sync keeps our entire team in the loop. An essential tool for any development team.
Eugene
Eugene
Product Manager, Prospex

FAQ

Before the next UAT round.

Questions about data handling? Read Security.

Do our testers need an account?
Not with the widget. Anyone who can see the Report button on the staging site can send a report. With the Chrome extension, the people you invite sign in with a code sent to their email.
We cannot change the UAT environment. Can we still collect reports?
Yes. The Chrome extension adds the report button on the URLs you list, with no script on the site. It runs in the tester’s own browser, so it also works behind a login.
Does it manage test cases or the sign-off?
No. SnagRelay collects the defects testers find, with the evidence. Test plans, cases and the final approval stay in the tool you already use for them. The reports go to your tracker, or wait in the SnagRelay inbox.
Where do the reports go?
Jira Cloud, Linear, GitHub, GitLab.com, Trello or Azure DevOps Services, one tracker per project. Without a tracker they stay in the SnagRelay inbox.
Can testers hide private data?
Yes. The Hide tool blacks out any part of the screenshot before it is sent, and nothing leaves the page until the tester clicks Send. For how the data is handled, see Security.
Can we run several UAT rounds?
Yes. Create a project for each round or environment, so the reports from one round do not mix with the next.
Do developers need a coding agent?
No. The report is an ordinary ticket. If a developer uses Cursor, Claude Code or Codex, the agent can read the same report over MCP.

Run the next UAT round with the evidence attached.

Start free