How a test heals itself
Record once, replay for free, and repair the test when the website changes, without hiding real bugs. The easy case, explained from the start.
See it work before you install it.
Every run in these videos is real: a real browser, real AI calls, and the costs and timings Saffron reported. Start with the tour, then watch a test heal three times, each change harder than the last.
Episode 0 · Getting started
Saffron in three minutes, from zero to green
Install, write a test in plain language, watch the AI agent record it once in a real browser, review the recording in your editor, then replay it with zero AI calls. Ends with the report and the three result states.
Three changes that break test suites, and what Saffron does about each
A renamed button, a page that disappears, and a step with nothing left to do. In every run the final check passes exactly as written, and nothing changes until you accept the proposal.
Healing at runtime
An A/B test removes a whole page and moves its fields into checkout. The agent takes over in the same browser, works out what the check was for, and finishes the run.
Healing by intent
A step that no longer needs doing. The agent finds proof the goal is already met and records a check for it. Then a real error at payment, which it fails red instead of healing.