Record a journey once. Replay it on every release.
Sign up, add to cart, pay: click through it in a browser shown inside Check’d, or describe it in plain English. Check’d writes down readable steps with screenshots and replays them on every run, without the AI and without brittle selectors.
On the Starter, Business and Team plans. Nothing to install.
Four ways in
Pick whichever is quickest for the journey in front of you. They all become the same steps.
Use your site
It opens inside Check’d. Click through once; each action becomes a step you can read.Describe it
Write the journey in plain English. The AI explorer does it once while you watch and saves the steps.Save a replay
Turn a real user session from session replay into a draft journey.Behind a VPN
A bookmarklet records in your own browser and sends the steps to Check’d.
Replays that survive a redesign
- Values that look generated, like hashes and CSS-in-JS class names, rank lower because they change between releases.
- A failed step becomes a finding with screenshots before and after, what was expected and what the page showed.
| Locator | How it finds the element |
|---|---|
| test id | data-testid, data-test, data-cy or data-qa, set by your developers |
| role and name | What a screen reader announces: button, “Add to cart” |
| label | The form label, such as Email |
| placeholder | The hint inside an empty field |
| text | The visible text, when it does not look generated |
| CSS | A stable id first, a CSS path as the last resort |
Fresh test data on every run
- A run makes each value once, so signing up and then signing in uses the same address.
- Values also come from the journey’s test data, the environment’s variables and its sealed test account.
| Template | Becomes |
|---|---|
| {{unique.email}} | qa.k3x9q2m1@example.com, new each run |
| {{unique.id}} | A short id unique to the run |
| {{random.digits:6}} | Six random digits |
| {{today+7}} | The date a week from now |
| {{card.number}} | From the environment, never stored in the journey |
| {{ask.code}} | Asked from you when the run reaches it |
Edit, reuse, run
Step 1: Check the steps
The step editor shows each step in plain words with its screenshot. Reorder, edit or remove them.Step 2: Split out reusable pieces
Turn the first steps into their own journey, such as signing in, and use it in other journeys.Step 3: Run on every release
Run one now or put it on a schedule, next to your site scans.Step 4: Approve heals
When the page changed, look at the new locator and approve it; a heal inside a piece updates the piece.
Prefer to let the AI explore?
Questions people ask
Recording, replaying, healing and test data.
Do I need to install anything to record?
No. Your site opens in a browser shown inside Check’d. You click and type as a customer would, and each action becomes a step. For sites our servers cannot reach, such as behind a VPN, a bookmarklet records in your own browser instead.
Does replaying a journey use AI?
Not usually. A recorded journey replays step by step without the AI. The AI is only asked, a limited number of times per run, when none of a step’s saved locators find its element, and that change is shown for your approval.
What happens when my page changes?
Every step keeps several ways to find its element: test id, role and accessible name, label, placeholder, visible text and CSS. The runner tries them in order and says when it had to fall back. A fallback becomes a heal you approve before it is saved; nothing changes silently.
How do journeys handle sign-ups and one-time codes?
Typed values are templates. {{unique.email}} gives a fresh address on every run and the same one again later in that run, dates like {{today+7}} stay current, card details come from the environment and are never stored in the journey, and {{ask.code}} asks you for a one-time code when the run gets there.
Can I describe a journey instead of recording it?
Yes. Write it in plain English, such as sign up, add a product to the cart and pay with the test card. The AI explorer performs it once in the hosted browser while you watch and saves its steps.
Which plans include journeys?
Recording, describing and replaying journeys are on the Starter, Business and Team plans. Recording time counts against your usage at the browser-minute rate.
Works with the rest of Check’d
- Production monitoringErrors, failed requests and slow pages from real users, in one inbox with your test findings.
- Session replaySee what happened before an error, with every input masked.
- AI explain and fixA plain-English cause and fix for any issue, then a pull request you review.
- Import from any docs linkSwagger UI, Redoc, Postman, ReadMe, Mintlify and more, or a file.
- For developersThe checked CLI, the MCP server and the SDKs, open source on npm.
Record your checkout today
Start free, then move to Starter when you want journeys on every release.