What QA actually runs before launch
"Fully tested" means nothing without the list. This is the list, the QA pass every build runs on staging before launch, published so you can hold any developer to it, including this one.
1 · Functional, the paths money and leads travel
Every form submits, validates, and delivers (to inbox and store). Every checkout completes in test mode: payment captured, order recorded, receipt emailed, refund working, the full pipeline, not just the happy path (declined cards, expired sessions, double-submits). Authentication: register, log in, reset password, log out, permission boundaries. Search, filters, pagination, feeds. Each pass gets ticked against the written scope from the working method, QA against the scope, not against vibes.
2 · Responsive and cross-browser, the devices your buyers use
Real device classes: phone (small and large), tablet, laptop, desktop-wide. Evergreen browsers: current Chrome, Safari, Firefox, Edge. The checks: layout holds at each width, navigation and menus behave, images render and crop correctly, tap targets are touch-sized, and the sticky elements (headers, WhatsApp float) do not eat the content. Testing happens on real hardware for the phone case, emulators miss the font-scaling and touch realities.
3 · Performance, the budget, measured
The Core Web Vitals budget runs on the staging build: LCP under 2.5s, INP under 200ms, CLS under 0.1 at the 75th percentile on mobile. Images sized and lazy-loaded where correct, render-blocking resources deferred, caching configured. Regressions get found before your customers feel them, the same measurement discipline the performance page uses in rescue work, applied preventively.
4 · Accessibility, the pass that keeps you out of trouble
Keyboard-only navigation through every interactive flow, visible focus states, contrast against WCAG AA, form labels and error states announced correctly, alt text on meaningful images, heading hierarchy sane. The accessibility page covers why this is a launch requirement rather than a nice-to-have, legal exposure lands on site owners, and the fix costs an afternoon before launch and a lawsuit-shaped number after it.
5 · SEO basics and content, the launch-minus-one-day pass
Canonical URLs, one h1 per page, title and description on every page, sitemap generated, robots.txt correct, schema valid, redirects mapped from any replaced URLs, 404 page branded and functional. Then the human pass: content proofread, phone numbers and emails correct everywhere, forms' recipient addresses verified, placeholder text hunted to extinction. The launch runbook picks up from here, QA is the last gate before it.
The honest fine print
QA cannot guarantee zero bugs, it guarantees the known paths were exercised and the known failure classes were checked. What it also gives you: a written list of what was tested, so nothing hides behind "fully tested." For stores, the checkout QA includes the payment triage checklist; for AI features, the eval gates from the AI-assisted build process run as well. The QA pass is included in every fixed-scope build, it is not an upsell, it is the definition of done.
Launching soon on someone else's "fully tested"?
Ask them for their QA list. If the answer is a shrug, this page is the checklist, and a scoped pre-launch QA pass costs less than the launch-day fire drill it prevents.
Want this process on YOUR project? Get a scoped quote, two minutes now, a written answer with price and timeline in two days.