Video · 0:45
Every target is recorded with several ranked locators and a fingerprint of the element it found. When the site changes and they stop matching, Kaabist finds the element again, writes the fix down as a proposal, and lets you promote it to a new version.
Key moments
Transcript
A program that worked yesterday. Every morning it opens the portal and clicks Export. Its locator has candidates: a test id, a role and name, the text.
The site is redesigned. Overnight the button moves, its classes are hashed and its label changes. Nobody told you.
The locator misses. None of the candidates matches a single element any more. Instead of guessing, the run stops on that step.
Kaabist finds what moved. It compares the page with the last good snapshot and finds the element that plays the same part: same place in the flow, same job.
It proposes the fix. The new locator comes as a proposal: the diff, the old and new screenshots, and the evidence. Nothing changes on its own.
You approve it. One click promotes it to a new version. The job carries on, and tomorrow's run uses the new locator.