用 TestSprite CLI 自动化测试 AI 生成网站

Claude Code tip: before you ship a vibe-coded site, have your agent 𝗰𝗹𝗶𝗰𝗸 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝗿𝗲𝗮𝗹 𝘂𝘀𝗲𝗿. Point the TestSprite CLI at your preview deploy, have it check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟮 𝗳𝗹𝗼𝘄𝘀 in a real browser, then fix every failure in one pass:

Accounts → Sign up with a fresh email, log out, log back in. Is your data still there? → Wrong password, empty form, an email that's already taken: does each one show a clear error? → Log in as user B and try to open user A's data. You should see nothing

Cart and checkout → Add, change the quantity, remove. Does the total update every single time? → Reload in the middle of checkout. Is the cart still there? → Apply a promo code where it shouldn't work. Does the total stay the same?

Forms and email → Submit every form with bad input: blanks, very long text, the wrong format → Use the unsubscribe link while logged out. Does one click actually do it?

The boring stuff that breaks first → Every nav link, on desktop and mobile width → Empty states: no items, no results, no notes yet → Back button after an action. Does the page still make sense? → Anything you changed in this PR, plus the flows next to it

Setup: npm install -g @testsprite/testsprite-cli testsprite setup

It writes the tests itself from the preview URL, and every failure comes back with a replay, the cause and a fix prompt your agent can apply.

The default medium effort is enough. Accounts are the most expensive group to get wrong, so raise effort to high when fixing those.

Send this whole post to Claude Code. If you need to, add this line at the end 👇 "Test my preview deploy, after checking it isn't on the production database. If it is, or there's no preview, use my local dev server on a test database (TestSprite's --local). If neither works, stop and tell me. If the preview needs a Vercel login, tell me how to create a Protection Bypass for Automation secret, then add the secret I send to the URL as x-vercel-protection-bypass, with x-vercel-set-bypass-cookie=true. Create two already-confirmed test accounts (A and B), and prefix everything you create with testsprite-. Send email only to my test inbox, and use test mode for payments. Keep the API key and bypass secret out of git and anything you show me. Run the phone-width checks (390×844) and any sign-up with an email code yourself in Playwright, and ask me for the code. List each failure with its replay and cause, counting a pass that skipped a step as a failure. Reproduce each one yourself with Playwright, then wait for my OK. Fix the ones that reproduced in one pass, list the rest as unconfirmed, rerun them once, and give me a pass/fail/n/a table for all 12 flows. Finally, delete only the testsprite- accounts and data, and remind me to revoke the bypass secret."