Browser and Computer-Use QA Pattern

Rocky’s public pages need more than syntax checks. Browser and computer-use QA catches the spacing, wrapping, and image issues that automated route checks often miss.

When to use it

• Public pages where layout and copy polish matter.
• Flows that require clicking, typing, or checking responsive behavior.
• Desktop app or browser state that cannot be verified from static HTML alone.
• Mobile and tablet checks where horizontal overflow or cramped chips often appear.

Checklist

• Load the route at desktop, tablet, and phone sizes.
• Check HTTP status, page title, canonical, and meta description.
• Inspect console errors and broken images after the page fully loads.
• Capture screenshots or contact sheets for representative routes.
• Review the pixels for clipped headings, awkward wrapping, duplicate images, and orphaned controls.

Pitfalls

• A green build is not visual QA.
• DOM text extraction can miss footer anchors or image text.
• Screenshots taken before images finish loading can create false broken-image reports.
• Do not click permission, payment, password, or secret dialogs unless the user explicitly asked for that operation.

Verification steps

• Save or inspect a contact sheet for the changed pages.
• Run a local route sweep before deployment and a live mapped-domain sweep after deployment.
• If a visual issue appears on multiple routes, fix the shared CSS cause and rerun the full pass.