Roadmap

Site checks

Automatic checks that your site still works the way you expect, every time something changes.

Planned. Not available yet. Details may change before it ships, and we'll announce it on What's new when it's ready.

They come in two kinds.

Quick checks

• A quick check is a short, plain-language test for one site, such as "the contact form sends a message to the office" or "the home page shows the service times". It visits a page or sends a form, then confirms the result: the right page or message comes back, certain text is or isn't shown, and a record would be saved or an email would be sent.
• Form and flow checks run in a safe sandbox. Nothing is saved, and no real emails or payments are sent.
• The assistant writes checks when it builds a page, form or flow for you, and you can ask it for more at any time.
• Before you publish a change, the checks related to it run against your draft, and the publish card shows which passed. If one fails, you'll see what went wrong and decide whether to publish anyway.
• They also run after a site-to-site or GitHub deploy (with an offer to roll back if any fail), every day if you like (with an email if something breaks), and whenever you ask.
• Quick checks don't use AI. They're billed in credits like your site's other usage. Having the assistant write or change checks uses assistant credits as usual.

Browser journeys

• A browser journey walks through your site the way a visitor does, in a real web browser: fill in a form, click buttons, check out, sign in, wait for the page's scripts, and catch script errors or broken layouts along the way.
• Journeys are built into Sherman Studio, with nothing extra to sign up for or install.
• They run after deploys, on a schedule and whenever you ask, rather than on every publish, because a full browser run takes longer.
• Like quick checks, journeys follow exact steps and expected results, with no AI judging, and they're designed not to send real emails or charge real payments.
• Journeys are optional. Because they use browser time, they're priced separately in credits, at a higher rate than quick checks, so you can turn them on for the sites where they're worth it.

There's no separate test mode or test copy of your site to manage: checks run alongside your normal editing and publishing.