In this video· click a step to jump to it
Test recording
Trace — register + in-app walkthrough v6 (fail if auth fails)
152,869 ms · 325 pixels changed
We built this regression test for gettrace.vercel.app — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against gettrace.vercel.app. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
// Set to true on any site that has a real signin. If auth was attempted
// (the register form was found and we tried to submit) but didn't
// complete, the test will throw at the end so the build surfaces as
// failed — silently swallowing auth failures hides real product issues
// (broken signup, invisible verification, etc.) behind a green build.
const REQUIRES_AUTH = true;
const DEMO_EMAIL = '[email protected]'•••'Lastest-Demo-202605141345!';
const DEMO_NAME = 'Lastest Demo';
const shot = (n, slug) => screenshotPath.replace('.png', `-${n}-${slug}.png`);
const settle = () => page.waitForLoadState('networkidle').catch(() => {});Checks run
Notes from the demo run
AI-generatedConversational product discovery (Trace) on a vercel.app domain. The demo walks the home + linked pages, opens /signup, fills email + Full Identity + Secure Password + ticked terms, then exercises the verification gate: the test JS-bypasses the cosmetic disabled state on Create Account and the server returns the real rejection (Please complete the verification and try again). Captures the verification-rejection state as the authenticated baseline.
- Distinctive form copyFull Identity instead of Name and Secure Password instead of Password is a small but on-brand touch that fits the conversational/identity-aware framing of the product.
- Clean single-column signupEmail + name + password + terms + submit, no OAuth-only pressure, no in-page upsell. Easy to follow.
- Disabled state is purely cosmetic; the real gate is server-sideThe Create Account button ships with disabled="" in the SSR HTML. Stripping that attribute via the devtools (or any browser-extension password manager that does not honour disabled) lets a user click submit, and the server returns the real check: Please complete the verification and try again. The implication: the disabled state is decoration, not protection — anyone bypassing it (autofill, screen readers, automation) routes the same load to your server-side challenge. Worth either making the gate visible (render the Turnstile / hCaptcha widget so users can complete it) or removing the cosmetic disabled so the failure mode is obvious from the first click.
- Non-standard field labels reject heuristic auto-fillersFull Identity / Secure Password do not match standard label heuristics (Name / Password) — password-managers and integration tests fall back to placeholder or type-based selectors. The placeholders (Jane Doe, masked password) read clearer than the labels.
Visual change
Share this run
This test was built for gettrace.vercel.app — claim it free
One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.


