Website QA checklist before launch

Choose the journeys and test environment

List the pages, browsers and devices in scope. Prioritise the main conversion journey, such as enquiry, booking or checkout, before less-used features. Use test accounts and a staging environment where available; agree which checks may run on the live site.

Download the website QA log

Record the build or release date, browser, screen size, steps and outcome. Mark checks you could not run instead of treating them as passes.

Test forms from input to notification

• Submit a valid enquiry and check its confirmation.
• Try missing required fields and invalid formats.
• Check whether an error keeps the visitor’s entered text.
• Check duplicate-click handling and a controlled failure case.
• Confirm the receiving inbox or system gets the submission once.
• Check the reply route, not only the on-screen success message.

Use clearly labelled test content. Agree on notification recipients before submitting tests so staff can distinguish them from real customers.

Check navigation, accounts and checkout

Follow menus, internal links, search and filters. Review empty states, unavailable items and the route back from a missing page. For accounts, check the agreed sign-in, sign-out and recovery flows using dedicated test users.

For checkout, use the payment provider’s test environment and approved test details. Check totals, required information, success/cancellation states and the order record. A live purchase is a separate authorised transaction, not a default QA step.

Check mobile and browser behaviour

On the agreed screen sizes, look for clipped content, horizontal scrolling, hidden buttons and overlays that block actions. Open the menu, complete the form and check the on-screen keyboard. Repeat important journeys in the agreed browsers; a screenshot alone cannot confirm functional behaviour.

Basic usability checks can include readable instructions, clear focus and meaningful error messages. Do not present a short launch checklist as a complete security, accessibility or performance audit.

Hand over findings and retest

For each problem, record reproduction steps, expected versus actual behaviour, environment and evidence. Prioritise issues by impact on the visitor’s task. After a fix, retest that journey and record any remaining limitations before launch.

For further planning, see BrowserStack’s website QA overview. Your own coverage should reflect the website and tools actually available to your team.