Replay and automation
Website checks without code
Autodocs workflows double as no-code website smoke tests: each run reports every step as passed, healed, failed or skipped.
THE PROBLEM
You find out a flow broke when a customer tells you
Sign-in, sign-up and checkout break quietly. Test suites need engineers. Any Autodocs workflow can serve as a no-code check that a flow still works.
Record a sign-in or checkout once and replay it to check your site still works. Every run reports each step as passed, healed, failed or skipped.
How it works
How does website checks without code work in Autodocs?
- 1
Record the flow once
Sign in, search, check out: whatever must keep working.
- 2
Replay it when you want a check
Ask an Autobot to run it, or run it on a schedule.
- 3
Read the result
Every step is listed as passed, healed, failed or skipped, with a summary of where it stopped.
- 4
Act on changes
A healed step means the site changed there; a failed step means the flow is broken.
Options and settings
Every option, in one table
| What you get | Detail |
|---|---|
| Per-step results | Passed, healed, failed or skipped for every step. |
| Run summary in words | What passed, what healed and where it stopped, without typed values. |
| Last run on the workflow | Passed or failed, and when. |
| Run status | `autessa browser-workflows run-status` shows the step a run is on and how many ran or failed. |
Who can do what
Permissions
| Who | Can |
|---|---|
| The person who recorded a workflow | Sees its steps, renames it, replays it and deletes it. Workflows are personal. |
| An Autobot | Runs the check and reports results to you in chat, by email or Slack. |
AI assist
Where AI helps
AI is used where it saves you work and is always visible: it writes the guide from your recording, and it finds elements that moved during a replay, marking those steps healed. You stay in charge of what gets published.
Connects to
How it fits with the rest of Autodocs and Autessa
FAQ
Website checks without code: questions
Can I test my website without writing code?
Yes. Record the flow in Autodocs and replay it; each run reports every step as passed, healed, failed or skipped.
Is this a replacement for a full test framework?
It covers no-code checks of real user flows. Teams with large engineering test suites usually keep them and use Autodocs for flows that non-engineers own.
How do I get told when a check fails?
Run it from an Autobot on a schedule; replies from scheduled runs can reach you by email or Slack direct message.
Try website checks without code on a task you do every week.
Record it once in Autodocs. You get the guide for your team and the workflow for next time.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Make Autessa Autodocs fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours