Skip to content

Give your next release
a testing team.

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

Request a pilot
Proposed validation experience with fictional checkout data
Demo runTest environment

User flows

What your customers need to complete.

Saved-card checkout

Agreed scope
Run complete1 of 2 failed

Checkout agentCompared the confirmation with saved records.

Scope agentFlagged retry behavior for review.

A returning customer places an order with a saved test card.

  1. Sign in with the test account.
  2. Add an item and select the saved test card.
  3. Place the order.
  4. Confirm that the order was saved.Failed

Approved expectation

A successful checkout saves one order and shows a confirmation.

Outside scope

Guest checkout, refunds and live payments.

Checks

Saved-card checkout

Run complete1 of 2 failed

Checkout agentCompared the confirmation with saved records.

Scope agentFlagged retry behavior for review.

Agreed checks

Test environment
Fictional saved-card checkout check results
CheckResultEvidence
Show a confirmationPassedDemo checkout screen showing Order confirmedConfirmation screen
Save the orderFailedSaved-order lookup found no record for this checkout.

The confirmation appeared. A lookup using the checkout reference found no saved order.

Investigated by Checkout agent

Approved expectation

A successful checkout saves one order and shows a confirmation.

Still unchecked

Guest checkout, refunds and live payments.

Findings

Evidence for your team to review.

Order confirmed, but not saved

Investigated by Checkout agent
Expected
One saved order after a successful checkout.
Observed
The success screen appears. A saved-order lookup using the checkout reference returns no record.
Reproduce
Sign in, add an item, select a saved test card and place the order. Compare the confirmation with the saved records.

Still unchecked

Guest checkout, refunds and live payments.

Review status

Awaiting your review

See how checks carry forward

Start with one user flow.

We test one user flow, then repeat the checks after your app changes. Initial pilots include setup and review by Nauro’s founder. Product validation is in development.

Request a pilot

  1. Agree what to test

    We review your app together and choose the user flow to test. Before testing begins, we confirm the expected results, exceptions and permitted actions in your test environment.

  2. 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.

  3. 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.

When your app changes, the checks keep up.

Each user flow keeps a record of what should happen, why it matters and which exceptions apply.

When behavior changes, you review the new expectation before we update the checks. Earlier results stay available for comparison.

Concept example of reviewing expectations and rerunning checks after a product change. These are not results from a live test.

Checkout adds a processing state

Orders are now saved in the background.

  1. Affected by the change

    The confirmation check needs review. The approved expectation still requires one saved order.

  2. Owner confirms the update

    Show processing while saving. Save exactly one order, then show confirmation.

    Retained with the previous expectation and its reason.

  3. Updated checks run again

    Confirmation follows the save
    Passed
    Exactly one order saved
    Passed

    Other checks are still pending.

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?

We start with your existing tests and identify what still needs checking in the agreed 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 compare the result with the behavior you confirmed and reproduce unexpected results. If the evidence is incomplete or the expected behavior is unclear, we flag it for review. We only mark the agreed user flow as passed when every required check passes.

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

Access to an agreed test environment, relevant documentation and existing tests. Before you grant access, we agree which data can be used, who can access it and which actions are permitted.

Tell us about your app.

Email a short description of your app, the user flow you want tested, your next release date and whether a test environment is available. Thomas will review the fit with you and agree the scope, access and timing before testing begins.

Email Thomas

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