In this video· click a step to jump to it
Test recording
CliqSpy — app walkthrough (authed)
44,282 ms · 0 pixels changed · matches baseline
We built this regression test for app.cliqspy.com — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against app.cliqspy.com. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const MARKETING_URL = 'https://cliqspy.com';
// PRE-CONFIRMED CREDENTIALS — user confirmed verify-email for these on 2026-05-17.
// Do NOT regenerate the stamp; the account is locked to this exact email.
const DEMO_EMAIL = '[email protected]';
const DEMO_PASSWORD = '•••';
const shot = (n, slug) => screenshotPath.replace('.png', `-${n}-${slug}.png`);
const settle = () => page.waitForLoadState('networkidle').catch(() => {});
const isAuthPath = (u) => /\/(login|signin|sign-in|signup|sign-up|register|verify|forgot)/i.test(new URL(u).pathname);
Checks run
Notes from the demo run
AI-generatedUpdated CliqSpy demo. After the user manually confirmed the verify-email link sent on the first run ([email protected]), the test was re-authored to bypass register and POST directly to /api/auth/login. The login form rendered cleanly (CS logo, dark-mode chrome, yellow Sign In button). Submit completed but the server returned 403 — likely a stale baked password (Date.now-time stamp re-computed in test code, not matching the original signup) or a CliqSpy-side password re-hash on confirmation.
- Dark-mode auth chrome with bright-yellow CTAsStill distinctive vs the white-background default in this category — login screen reads tight and brand-coherent.
- Resend Verification Email surfaced inline on the gate screenThe verify-email gate prefills the user's email in a readonly input + one-click resend. After the user clicked the verification link, the account is now active in CliqSpy's DB.
- Inline 'Forgot password?' link below Sign InBottom-right of the Sign In button. Standard placement; would help here since the test couldn't reproduce the original password.
- POST /api/auth/login returned 403 with otherwise-valid credentialsConsole showed a 403 from the auth endpoint after submit. Could be password-mismatch (the test re-baked the credentials at run time, so the password no longer matches what was originally hashed), session timing, or anti-replay header. Worth checking whether the login endpoint surfaces a user-visible error message — the form just stayed on /login silently.
- Verify-email gate before any dashboard preview (still applies)Even with a confirmed account, the previous run's gate-first UX hasn't changed. Consider letting unverified users see a read-only product surface.
- /dashboard (authed)·Login POST returned 403 — server rejected the pre-confirmed credentials
Share this run
Proof your app is not AI slop
This test was built for app.cliqspy.com — 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.