Deploy checks with AI buyer personas
Ship changes without losing sign-ups.
You want to ship on Friday and know the buyer’s path still works on Monday. A release can change a menu link, a plan card or a signup path without failing a test. Barbwire sends the same personas after each production deploy.
Check your next deploy- The same personas after each production deploy
- Your CI tag: branch and commit
- Emails you when it stops buying
Your tests pass. The buyer’s path still broke.
Unit tests check code. End-to-end tests check the clicks you wrote down. Neither tells you that a menu link now opens the wrong page, or that a plan card lost its price.
You find out from a drop in signups, with no version to blame.
What you set up: one token, one workflow file.
- On the Deploy checks page, make a token. Save it in GitHub as the secret
BARBWIRE_TOKEN. - Copy the workflow Barbwire gives you into
.github/workflows/barbwire.ymland push it. - When Vercel, Netlify or another GitHub integration reports a successful production deploy, the workflow sends your personas in. If your pipeline deploys by itself, add one step after your deploy step instead.
By default the personas of the site’s last test go. Pick others under “Sent on each deploy”. A version already on the site is not sent twice. Each persona counts as one run.
What you see: the same persona, before and after the release.
Each deploy run appears in your Runs list with the word “Deploy” and your CI tag: branch and commit. Next to it stands the build version Barbwire detected on your site, or the date and time. Open the run from this deploy and the run before it. Same persona, same start page. Read where each one stopped and what it said at that step.
Watch a persona, and Barbwire emails you when it stops buying after a run. The mail names the deploy tag.
A yes on the last version and a no on this one shows what the release cost, with the screenshot.
Fix it. The next deploy confirms it.
Open the step and its screenshot. Copy the fix as an issue. When the fix ships, the deploy check sends the same persona again. Runs vary a little, so trust a flip, not a one-point move. A finding that shows up in run after run is yours. One seen once may be noise.
Limits
Personas test public pages. They stop at login walls and never type into or submit a form. A captcha or bot wall ends the run, the report says so, and the run is free. When your runs are used up, the step fails with a message that says so. It runs after the deploy, so it cannot stop one.