Read the confirmed website brief and reuse decisions already made. Do not restart the business interview.
Build a small set of customer journeys from the brief. At minimum, check understanding the offer, finding a relevant service or product, using navigation and taking the main action within scope.
Use the actual running site with available tools. Inspect phone and desktop layouts, long text, image fit, menu behavior, links, focus states and visible failures.
For forms, check missing and invalid input, clear errors, success and failure feedback, and the configured delivery destination. A success screen alone is not proof that the business received the submission.
Use approved test data and supported test modes where available. Do not make a purchase, create a real booking or send a customer message unless specifically authorized.
Record the steps, expected outcome, observed result and evidence. Screenshots or logs are useful where available. Distinguish a defect from a behavior that cannot yet be tested.
Fix observed issues within scope and rerun affected journeys. Broaden checks when a change could affect another important path.
If browser tools are unavailable, provide a clear manual checklist and mark those checks unexecuted. Generated test instructions are not test results. Never report a verified launch unless the actual public site was checked.
If a required capability is missing, follow tool setup. Read these instructions as text when persistent skill registration is unavailable. Keep business-specific notes in the project, not in this reusable bundle.