sakioriProduct
Self-healing UI tests that show their repairs.
Sakiori turns the flows your QA team clicks through into automated tests. When the UI changes, it repairs them and shows you exactly what it changed. When something’s really broken, it tells you why.
Healing you can check.
It finds the moved button, then shows its working
When a step’s element isn’t where it was recorded, Sakiori lists every way it looked, in plain words:
✕ Where it was when recorded · ✕ A button named “New item” · ✓ Closest match “Add item”, 99% sure
It understands what an element does, not just what it’s called: a button that submits a form, a link to a page, the field labelled “Price”. So “Create” can become “Save” and the test still clicks the right thing.
Not sure? It stops and asks
Sakiori only repairs a step on its own when it’s confident. Below that, the run stops for review and shows its best guess with the screenshots. You answer “Yes, use ‘Save’ and run again” or pick a different element. Your answer updates the test and teaches the next run.
Red doesn’t just mean red
When a step fails, Sakiori gives the likely cause in plain terms: real bug, UI change, timing, test data or environment. It shows the evidence behind it: failed network requests, the text that never appeared, and a screenshot from the moment it failed. Unclear cases are marked “needs your call” instead of being guessed.
Two ways to make a test.
If you can describe it, you can test it.
Type steps the way you’d write them in a test case. A live preview shows how each line is understood before you save, then Sakiori performs the steps in a real browser to build the test.
Click Sign in Fill Price with 24.50 Check "Item created" appears
Click through it once. That’s the test.
The recorder captures each click, entry and choice, along with what appeared on screen afterwards, and uploads the test straight to your workspace. Passwords are masked at the moment they’re typed.
One review queue for everything.
Heals to confirm and failures to triage come into a single queue, with “Recorded vs now” screenshots and the reasoning behind each decision. Use J and K to move through it and A to accept.
Built for real test suites.
Modules and tags
Group tests by area of the app (Auth, Checkout, Inventory) and label them (#smoke, #regression).
Suites
Pick modules or tags and run them together across several environments.
Starts from
Chain tests: “Edit the item” starts from “Create an item”, which starts from “Log in”. Each test still runs on its own, and when a setup test fails, the problem is reported once, on the test that broke, instead of on everything after it.
Variables
{{unique}} gives every run fresh test data. “Remember the order number as {{order}}” captures a value from the page and reuses it in later steps.
Environments
Run the same test on Staging, a feature build or a redesign, and compare the results side by side.
Know which tests to trust, and which to fix.
Home
What needs you today: items to review, failing tests, every test’s latest result on every environment, and runs over the last 14 days.
Insights
How often Sakiori’s choices were right when someone checked, whether its confidence holds up, which steps keep moving, and how much time is lost waiting for elements that moved.
Run view
A 150-step run you can read in ten seconds. A step map shows every step at a glance, coloured by result. Routine steps fold away, and the run opens at the step that stopped, with screenshots of the moment it happened. J and K jump between the steps that need attention.
Stop fixing tests that were never wrong.
Record your first flow in a couple of minutes. The next time the UI or flow changes, see what Sakiori repairs, and how it shows you.