AI-assisted browser testing

Test with confidence.
Understand every failure.

Record and replay browser workflows, get AI-assisted guidance when tests fail, and report quality findings to your team.

Start freeSee how it works

Built with QA teams who test busy SaaS applications.

How it works

Checkout as a guest● Recording
  1. 01Go to /shoprecorded
  2. 02Click “Add to cart”recorded
  3. 03Click “Checkout”recorded
  4. 04Fill “Email”recorded
  5. 05Click “Place order”recorded

Recording in Chrome

Each action becomes a step

Clicks, typing, dropdowns, file uploads, new tabs and more. You can read and edit every step.

ClickTypeDropdownsUploadsNew tabs

01 · RECORD

Use your application. Each action becomes a step.

Record with the TestPulse extension.

02 · REPLAY

Choose a server. It runs in a private window.

Staging, UAT, any server you add.

03 · INVESTIGATE

Evidence, a likely cause and AI-assisted guidance.

The step that failed, in plain words.

04 · REPAIR OR REPORT

Fix only the affected steps, or report to your team.

Nothing changes without your approval.

5kinds of evidence kept with every failure
4steps from recording to a report
1person approves every change to a test
0cookies or browsing data cleared

Why test results lose trust

Passing is not the same as working.

Teams spend time on repeated workflows, fragile steps and failures that nobody can explain.

Repeating the same workflow

The same browser journey, checked by hand, release after release.

Tests break when a label moves

A changed label, structure or position can break a step that still works.

Defect or test problem?

A failure can be a product defect, or timing, sign-in, network or environment.

Re-recording a whole workflow

Often only one step needs to change.

Issues without context

Bug reports filed without what the browser was doing.

Failures, tickets and fixes drift apart

Nothing connects the failed run to the ticket and the change.

The basics

Chrome extension

Record and replay in Google Chrome.

Your own Chrome

Tests run in a private window. Cookies and browsing data are never cleared.

Masked

Password fields are masked in failure screenshots.

Your approval

Every change to a test needs a person to approve it.

Try it

Rename a button. See what TestPulse says.

Flip the switch to ship a release that renames the button, then watch the replay.

Checkout

Blue mug · 1 item$12.00
sam@company.com
Place order

Replay on staging

Waiting for a release.

Likely cause

Element not found

Step 5 looks for “Place order”. A button labelled “Pay now” is in the same place.

AI-assisted guidance

Possible explanation

The label may have changed in a recent release. Check the new label, then edit or re-record only this step.

Results you can trust

A test should not pass only because automation managed to continue.

Checked or only performed

Each result shows which steps were checked and which were only performed.

1Done
2Done
3Checked
4Done
5Checked
Checked: the result was verifiedDone, not checked: the action ran

No guessing

If two elements look the same, the step fails instead of using the wrong one.

PayPay

2 MATCHES · STEP FAILS

Waits for your application

TestPulse waits for loading screens and network activity before each step.

Loading→Ready→Step runs

Flaky tests are marked

A test that fails and then passes on its retry is marked as flaky.

Last runs of “Checkout as a guest”

PassedFailed, then passed on retry

Run failed→Retry passed→Flaky

Test evidence

Test evidence for every failure.

Everything you need to start an investigation, kept with the run. Select one to see what is kept.

Video of the run
Screenshot
Email••••••••••maskedPay now
Page snapshot
1<form id="checkout">2  <input name="email">3  <input type="password"4    value="[hidden]">5  <button>Pay now</button>6</form>
Network requests
GET/api/cart200
POST/api/cart200
GET/api/shipping200

Sign-in headers and cookies are removed.

Console errors

No console errors in this run.

An error would show here, with the step it came from.

The step that failed, in plain words

Shown with the video, screenshot and network log.

A likely cause

Element not found, timing, sign-in, network, or a possible product defect.

AI-assisted guidance

Possible causes and next steps. It never changes a saved test.

Maintenance

Maintain tests with less rework.

01

Re-record only the affected steps

TestPulse replays up to the broken step, you record the replacement, and it runs the rest.

12345678
Replays up to the broken stepYou recordRuns the rest

02

Accept a suggested element

When an element changes, TestPulse suggests the closest match. You decide whether to use it.

Recorded

Place order

Closest match

Pay now

03

Keep a history

Every change is saved as a version. Any earlier version can be restored.

Version history

v4 · current

Steps 5 to 6 re-recorded. Not run yet.

Release confidence

See what has been tested before you release.

For each release, TestPulse shows what has been tested, what failed and what is flaky. It gives a simple label: Ready, At risk or Not ready.

AT RISKRelease 2.14
Checkout 8/8Account 5/6Billing 3/41 flaky
1Product defect
1Test needs update
0Environment
1Flaky

Example release. Choose which folders a release must cover, and see what is blocking it.

Who it is for

One failure, useful to the whole team.

04 · Fill “Email”checked
05 · Click “Place order”failed
Re-record from step 5Copy bug report

Product defect
Test needs update
Environment
Flaky

step 5 · Click “Place order”
element not found after 10.0s
network GET /api/cart 200
console no errors
Copy bug reportElements that need a test ID

Fit check

Is TestPulse a fit today?

Four quick questions. An honest answer.

Question 1 of 4

Do you test in Google Chrome?

FAQ

Questions and answers.

Google Chrome, through the TestPulse extension.

Not today. Tests run in your own Chrome, in a private window, one at a time.

No. TestPulse never clears cookies, cache or browsing data. It runs tests in a separate private window.

So each run starts in a clean private window, separate from your everyday browsing.

Yes. Add each server, choose one when you run, and TestPulse uses that server’s address and login test.

TestPulse shows which step failed and why. You can edit that step, re-record the affected steps, or accept a suggested element. Nothing changes without your approval, and earlier versions can be restored.

A passed test means every step ran. Steps with an expected result were checked. Steps without one are shown as “done, not checked”.

Yes. Recordings saved with earlier versions continue to load.

No. AI-assisted guidance only explains failures and suggests next steps. Every change to a test needs a person to approve it.

For a failed run, it receives the steps (with passwords hidden), the error, failed network requests, console errors, a shortened page snapshot (with password fields hidden) and the failure screenshot. AI is optional.

Yes. There are three roles. Admins manage servers, releases and integrations. Members create and run tests. Viewers can view results and report problems.

This is in development.

TestPulse is not the right fit today if you need tests to run in the cloud, in parallel or on a schedule; tests started from CI/CD; Firefox, Safari or mobile apps; or API-only testing.

Build confidence in every release.

Install the extension, record a workflow, and replay it on every release.

  1. 01

    Install the extension

    Add TestPulse to Google Chrome.

  2. 02

    Allow it in Incognito

    Tests run in a private window, so your own cookies and sessions stay as they are.

  3. 03

    Record your first test

    Use your application. Each action becomes a step.

Start freeLog in