Getting started

Sakiori turns the flows your QA team clicks through into automated UI tests. When the app changes, it repairs those tests and shows you exactly what it changed. When something is really broken, it tells you the likely cause.

What you need

• Sakiori, running locally. A hosted version is on the roadmap.
• Chromium, which runs the tests.
• Chrome, if you want to record flows with the Sakiori Recorder extension.

The three steps

1. Capture a flow. Record it in Chrome or write it in plain English. Sakiori performs the steps once to learn the page, then saves the test.
2. Run it. Run one test or a whole suite on one or more environments.
3. Review what changed. Repairs and failures land in the review queue. Confirm a repair with one keystroke and the test is updated for good.

Your first test

Pick a flow you already click through every release, such as creating an item:

Click New item
Enter "Desk Lamp {{unique}}" in Name
Choose "Hardware" in Category
Click Create
Check "Item created" appears

The last line matters. Sakiori checks that each step still produces what the recording saw happen, which is how it tells a moved button from a broken one.