sakioriHow it works
Record once. Run anywhere. Review what changed.
Three steps. The first two save you time. The third is why you can trust the result.
1. Capture the flow.
Record or write it
Click through it once with the Sakiori Recorder for Chrome, or type the steps in plain English:
Click New item
Enter "Desk Lamp {{unique}}" in Name
Choose "Hardware" in Category
Click Create
Check "Item created" appearsSakiori performs the steps once to learn the page, then saves the test.
2. Run it on every environment.
Looks the way a person would
Run one test or a whole suite on Staging, a new build or a redesign. When the app has changed, Sakiori looks for each element in order:
- where it was when recorded,
- then by its name and label,
- then by what it does on the page.
It continues only when it’s confident it found the right one, and when the step still produces what the recording saw happen.
3. Review what changed.
Every stitch, in plain sight
Every repair lands in Review, with the recorded page next to today’s page and the element outlined on both. Confirm it with one click and the test is updated for good. When Sakiori isn’t sure, it stops and lets you pick the right element. When something is genuinely broken, it tells you the likely cause.
Button moved into form footer and renamed.
Want the details?
The docs cover the recorder, plain-English steps, reviewing repairs and running suites across environments.
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.