Practical QA guides
Practical, tool-agnostic QA: what to check before you launch a web app, what silently breaks after, and how to test the flows static checkers skip. Every guide is useful with or without Prufa — the checklists stand on their own.
Start here: Website QA checklist before launch
-
Test your analytics before launch
A loaded analytics snippet can still record nothing. What breaks before launch — and how to check a beacon actually fires, not just that the tag is there.
-
Test your website on mobile before launch
What breaks on mobile before launch — sideways scroll, tiny tap targets, mobile-only JS errors — and how to get a verdict, not a phone-frame preview.
-
Test your login flow before launch
What breaks login flows before launch, ranked — and how to verify the whole loop: you sign in, the session sticks, locked-out users recover.
-
Test your password reset flow before launch
What breaks password reset flows, ranked — and how to verify the whole loop: the email arrives, the one-time link works, the new password logs you in.
-
Test your contact form before launch
What breaks contact and lead forms, ranked — and the one pre-launch check no external tool can do: confirm the email actually arrived.
-
Test your checkout flow before launch
What breaks checkout flows, ranked — and the safe way to verify each before launch: walk the flow up to the payment wall, no real card charged.
-
AI QA agents vs traditional e2e suites when each wins
Decision guide for teams with a Playwright or Cypress suite: 6 questions, 5 places hand-written e2e still wins, 5 where agentic QA wins, switch/stay/layer
-
Vibe coding exposed API keys: how they leak, how to check
Vibe-coded apps leak API keys via client-bundle hardcodes, git history, and the Supabase service_role mix-up. How to check, fix, and what a scan misses.
-
Vibe coding support after launch: keep your app running
Vibe coding support after launch: the four things that silently rot a working app from the outside, and the periodic functional re-check that catches them.
-
Client site QA checklist: the agency pre-delivery list
A repeatable pre-delivery QA checklist for agencies, ordered by what breaks across 49 launches — with the flow checks others skip and a forwardable report.
-
How to test a vibe-coded app: the 6-step process
The ordered process to test a vibe-coded app before launch, sequenced by a June 2026 audit of 49 launches where 78% shipped a critical bug.
-
Website launch checklist for indie hackers
In a June 2026 audit of 49 launches, 78% shipped a critical bug day one. An 8-item launch checklist for indie hackers, ordered by what breaks.
-
Is my vibe-coded app production ready? a scored assessment from 49 launches
Score your app against a 49-launch audit. 22% ship with no criticals; 73% ship with one; 4% need to hold. Six questions, ten minutes, real data.
-
Test your signup flow before launch
Five things that break signup flows, ranked by how often they show up, with a 60-second audit that walks the flow end-to-end.
-
Vibe coding testing checklist: 10 things to verify before you ship
Ten things to verify before you ship a vibe-coded app, grounded in a 49-launch audit. Each: failure mode, Prufa check, signal, 5-min manual fallback.
-
QA for vibe-coded apps: what actually breaks
What actually breaks in vibe-coded web apps, in what order, and what to do before launch. Data from 49 fresh launches, June 2026.
-
Website QA checklist before launch, ordered by what actually breaks
A pre-launch QA checklist ordered by real failure data from 49 audited launches: analytics first, then forms, links, SEO basics, consent, and user flows.