Give your next release
a testing team.

Agents explore your app, investigate what breaks and turn findings into checks for the next release.

Start with one user flow.

Agents start from a link to your app and test the user flow that matters most, then repeat the checks after your app changes. Pilots are free and founder-assisted: Nauro’s founder helps when you want it. Product validation is in development.

Request a pilot

Send a link
Share a link to your app’s test environment and say what agents may do there. They map the app, pick the user flow that matters most and start testing. Redirect them at any time, or share test accounts and documentation so they can cover more.
Get a report
Nauro runs the checks and investigates unexpected results. You receive the evidence, steps to reproduce problems and a list of anything we could not check.
Check the next release
After your next product change, we repeat the checks and compare the results. You can see what still works and what needs attention.

Checkout after payment update

Your team: Test checkout after the payment update.
Nauro: Worked for 8m
17 Oct
1. 10:00
  Focus set: payments changed
2. 10:01
  Run 1 · shop-0.18.3
  
  Passed: Click · DS-4819 · Order saved
  
  Passed: Keyboard · DS-4820 · Order saved
  
  Failed: Double click · DS-4821 · No order
3. 10:09
  2 findings · Nauro named this exploration
Nauro: 2 findings.
- Confirmation without an order, fixed
- Delivery cost after address, to review
Your team: Real bug. Fixed in shop-0.18.4. 17 Oct, 11:20.
Nauro: Worked for 1m
18 Oct
1. 09:30
  Your team shipped the fix · shop-0.18.4
2. 09:42
  Run 2 · recheck passed · shop-0.18.4
  Passed: Double click · DS-4822 · Order saved
Nauro: Recheck passed: DS-4822 saved.

Checks

2of 2

Rechecks passed

2 checks were not repeated after this change.

Findings

1 fixed · 1 to review

Checks by run
Check	Run 1	Run 2
Click: order saved	Passed	Not repeated
Keyboard: order saved	Passed	Not repeated
Double click: confirmation shown	Passed	Passed
Double click: order saved	Failed	Passed

Findings

Confirmation without an order Fixed . Bug, high impact. Recheck after fix, double-click on Place order: no order saved in Run 1, order saved in Run 2.
Delivery cost after address To review . Needs user test, not rated.

FixedBug, high impact.

Confirmation without an order

Recheck passed: DS-4822 saved

Your decision

Bug confirmed. Fixed in shop-0.18.4

Reproduction

Before fix · shop-0.18.3

Step 1 · 00:00 · Fresh checkout

demo-shop.example/cart

Your cart

Canvas tote × 1$24.00

DeliveryCalculated later

Step 2 · 00:14 · Double-click Place order

demo-shop.example/checkout

Place order, clicked twice

POST /api/orders00:14.01, DS-4821Canceled

POST /api/orders00:14.18, DS-4821409 checkout locked

Step 3 · 00:15 · Confirmation shown

demo-shop.example/checkout

Order confirmed

DS-4821

Step 4 · 00:20 · Order lookup

demo-shop.example/admin/orders

GET /admin/orders?reference=DS-4821

No matching order

0 records at 0s, 2s and 5s

Checkout, Navigate, 00:00: Fresh checkout
Double click, Click, 00:14: Double-click Place order
Confirmation, Observe, 00:15: Confirmation shown
Lookup, Check, 00:20: Order lookup

Expected

Rule: Confirmed means saved

A confirmation means the order is saved.

Actual

Before fix · shop-0.18.3

Confirmed on screen, never saved.

What the customer saw

Browser

demo-shop.example/checkout

Demo shop

Order confirmed

DS-4821

Canvas tote × 1$28.00

What was saved

Order lookup

GET /admin/orders
?reference=DS-4821

No matching order

No record at 0 seconds
No record at 2 seconds
No record at 5 seconds
No record in the database

How this was checked

Requests: 00:14.01 POST /api/orders · DS-4821 · Canceled00:14.18 POST /api/orders · DS-4821 · 409 checkout locked
Sources: Browser recording, network trace, order lookups at 0, 2 and 5 seconds, read-only database check.
Limits: Only the double click lost the order; click and keyboard saved. The trace shows the mismatch, not its cause in the code.

After fix · shop-0.18.4

The same double click, confirmed and saved.

What the customer saw

Browser

demo-shop.example/checkout

Demo shop

Order confirmed

DS-4822

What was saved

Order lookup

GET /admin/orders
?reference=DS-4822

1 matching order

Recheck after fix

Same behavior: double-click on Place order

Check results before and after the fix
Check	Run 1 · before fix	Run 2 · after fix
Confirmation shown	Passed	Passed
Order saved	Failed	Passed

Run 2: order DS-4822 on shop-0.18.4, 18 Oct

To reviewNeeds user testNot rated.

Delivery cost after address

Your decision

Waiting for your team

Reproduction

Step 1 · 00:03 · Product price

demo-shop.example/tote

Canvas tote

$24.00

No delivery estimate

Step 2 · 00:07 · Cart

demo-shop.example/cart

Your cart

Subtotal$24.00

DeliveryCalculated later

Step 3 · 00:12 · Address entered

demo-shop.example/review

Review your order

Delivery$4.00

Total$28.00

Product, Navigate, 00:03: Product price
Cart, Navigate, 00:07: Cart
Address, Type, 00:12: Address entered

Expected

No rule agreed yet. Only people can say if the total is clear.

Actual

Delivery cost shows only after the address.

Before the address

demo-shop.example/cart

Your cart

Canvas tote × 1$24.00

DeliveryCalculated later

After the address

demo-shop.example/review

Review your order

Subtotal$24.00

Delivery$4.00

Total$28.00

0 people observed
3 of 3 attempts

Next: ask people to find the total.

How this was checked

Sources: Browser recordings of 3 checkout attempts.
Limits: No usability threshold agreed. No claim about confusion or conversion.

Your team: Test signup and a first project.
Nauro: Worked for 7m
17 Oct
1. 14:29
  Focus set: new customers
2. 14:30
  Run 1 · shop-0.18.3
  
  Passed: Standard · account and project saved
  
  Passed: Double click Create account · 1 account
  
  Passed: Back, then resubmit · 1 account
3. 14:36
  No findings · Nauro named this exploration
Nauro: Three ways in, one account each. No issues found in these checks.

Checks

3of 3

Checks passed

Run 1 · shop-0.18.3

Findings

No issues found in these checks.

Checks by run
Check	Run 1
Standard: account and project saved	Passed
Double click Create account: one account	Passed
Back, then resubmit: one account	Passed

Invite a teammate

Your team: Test inviting a teammate.
Nauro: Worked for 5m
16 Oct
1. 15:19
  Focus set: team invites
2. 15:20
  Run 1 · shop-0.18.2
  
  Passed: Send invite · Pending
  
  Passed: Resend · still 1 Pending
  
  Not completed: Check inbox · no access
3. 15:24
  1 coverage gap · Nauro named this exploration
Nauro: Invites sent. 2 checks need inbox access.
- Inbox not checked, coverage gap

Checks

2of 4

Checks passed

2 checks not completed

Coverage gap

Needs inbox access

Checks by run
Check	Run 1
Send invite: shows Pending	Passed
Resend: still one Pending	Passed
Inbox receives invite	Not completed
Join link works	Not completed

Findings

Inbox not checked Coverage gap . Coverage gap: no inbox access.

Coverage gap

Inbox not checked

Open settings

Reproduction

Step 1 · 00:00 · Enter teammate

demo-shop.example/team

Invite a teammate

Recipient

[email protected]

Step 2 · 00:06 · Send invitation

demo-shop.example/team

Invitation sent

Status: Pending

Step 3 · 00:08 · Stop at access

demo-shop.example/team

Inbox access not granted

Teammate, Type, 00:00: Enter teammate
Send, Click, 00:06: Send invitation
Inbox, Check, 00:08: Stop at access

Expected

Rule: Missing access is not a failure

The invite arrives and its join link works.

Actual

The app says sent. No inbox to confirm.

What the app showed

Browser

demo-shop.example/team

Invitation sent

Status: Pending

Test inbox

Not connected

No inbox access

Sent, observed
Pending, observed
Inbox, not completed
Join link, not completed

How this was checked

Limits: Receipt and the join link were not observed.

Queue a review

Your team: Test queueing a review.
Nauro: Worked for 2m
18 Oct
1. 10:10
  Focus set: review handoff
2. 10:11
  Call · review-0.4.1
  
  Failed: queue_review · req-2048 · No review ID
3. 10:12
  1 finding · Nauro named this exploration
Nauro: The review was saved as pr-2048, but the reply left out its ID. The agent can’t check on it later.
- Reply leaves out the review ID, to review

Checks

1of 2

Checks passed

Run 1 · review-0.4.1

Findings

1 to review

Checks by run
Check	Run 1
Backend saves the review	Passed
Reply includes the review ID	Failed

Findings

Reply leaves out the review ID To review . Bug, medium impact.

To reviewBugMedium impact.

Reply leaves out the review ID

Your decision

Waiting for your team

Reproduction

Step 1 · 00:00 · Queue a review

review-agent

queue_review

request_id: req-2048

Step 2 · 00:01 · Read the reply

review-agent

statusqueued

messageReview queued

pending_review_id missing

Step 3 · 00:03 · Check the backend

review-agent

request_id = req-2048

Pending review exists

pending_review_id: pr-2048

Call, Call, 00:00: Queue a review
Reply, Observe, 00:01: Read the reply
Backend, Check, 00:03: Check the backend

Expected

Rule: A saved review returns its ID

The reply includes pending_review_id.

Actual

The reply said “Review queued”, with no ID.

What the caller received

MCP reply

queue_review · req-2048

{
  "status": "queued",
  "message": "Review queued"
}

pending_review_id missing

What was recorded

Lookup

request_id = req-2048

Pending review exists

pending_review_id: pr-2048
state: pending

How this was checked

Sources: Captured MCP request and reply, response schema, backend lookup for req-2048.
Limits: The review was saved. Only the reply was wrong.

Settings

Demo shop

Addresshttps://demo-shop.example
EnvironmentPreview / staging
IdentitiesTest accounts
DataSynthetic
Order lookupsRead-only
PaymentsSandbox
Test inboxNot connectedInvite a teammate
Live chargesBlocked
Other recipientsBlocked

Example only. No credentials, no connections.

When your app changes, the checks keep up.

After your fix ships, agents repeat the same behavior and compare the runs. When expected behavior changes, you review the new expectation before we update the checks.

Recheck after fix

Run 2

Same behavior: double-click on Place order

Check results before and after the fix
Check	Run 1 · before fix	Run 2 · after fix
Confirmation shown	Passed	Passed
Order saved	Failed	Passed

Frequently asked questions

What do I get from a pilot?

A report showing what passed, what failed and what could not be checked, with evidence and steps to reproduce problems. We retain the checks for another run after your app changes. Your team decides whether to release.

We already have automated tests. Where does Nauro help?

If you share your existing tests, we look for what they leave unchecked in the user flow. The pilot focuses on those gaps and on investigating unexpected results. There is no need to replace your Playwright, Cypress or other tests.

How do you check that a reported bug is real?

We reproduce unexpected results and link each finding to its evidence. When the expected behavior is our inference rather than something you confirmed, we mark it as a question for you, not a bug. A user flow passes only when every check you confirmed passes.

What access do you need, and how is our data handled?

A link to a test environment and the actions agents may take there are enough to start. Test accounts and documentation let agents cover more. You choose which data agents may use and which actions are allowed before they start.

Want us to test your app?

Leave your email with a link to your app and what agents may do there. Once the limits are set, agents start exploring.

For developers using coding agents.

Nauro’s decision system is available today. Keep approved decisions and their reasons available across coding sessions.

Use the decision system

Send a link

Get a report

Check the next release

Checks

Findings

Confirmation without an order

Your decision

Reproduction

Expected

Actual

What the customer saw

What was saved

After fix · shop-0.18.4

What the customer saw

What was saved

Recheck after fix

Delivery cost after address

Your decision

Reproduction

Expected

Actual

Before the address

After the address

Checks

Findings

Checks

Findings

Inbox not checked

Reproduction

Expected

Actual

What the app showed

Test inbox

Checks

Findings

Reply leaves out the review ID

Your decision

Reproduction

Expected

Actual

What the caller received

What was recorded

When your app changes, the checks keep up.

Recheck after fix

Want us to test your app?

For developers using coding agents.