Write the browser and device coverage before calling a website ready to launch.

A fictional studio is refreshing its portfolio. Its desktop gallery works in Chrome, but that check leaves mobile navigation, Safari and the downloadable project brief untested. The release owner needs to see those gaps before making the launch decision.

Build the test scope around visitor journeys:

• Define the exact site section and release version • List what a visitor must complete, such as opening a project, navigating back and downloading its brief • Choose browser, device and viewport combinations, with a reason for each • Give each test case and browser/device combination its own tracker row • Agree which failures block release and who can approve an exception

If time runs short, record the untested coverage and its owner. A passing desktop case cannot stand in for a mobile case that nobody ran.

The preview is the actual Set the launch test scope worksheet from the Website Launch QA Kit. It includes a five-page editable Word packet, matching print PDF, Excel tracker with 40 prepared rows, a fictional completed example and Quick Start.

This is a manual QA organizer. It does not run tests, certify accessibility, scan for vulnerabilities or authorize a launch.

Get the digital kit: https://contra.com/payment-link/ADjcdlD6-website-launch-qa-kit