Browser Automation QA for Public Pages

A public page can return HTTP 200 and still look broken. Browser automation helps Rocky inspect the rendered page, not just the server response.

Official Hermes Agent docs: https://hermes-agent.nousresearch.com/docs/reference/tools-reference

Browser QA checklist

• Page loads successfully on the intended URL.
• Canonical, title, and meta description are correct.
• No console errors or failed critical requests.
• Images load with nonzero natural dimensions.
• Mobile viewport has no horizontal overflow.
• Headings and buttons are not clipped.
• Forms, filters, and search controls work.
• Footer and navigation remain visible and usable.

Desktop and mobile pass

Run at least one desktop viewport and one phone-sized viewport for user-facing pages. For visual releases, create a contact sheet so several routes can be reviewed at once.

Common pitfalls

• Checking domcontentloaded before hero images finish loading.
• Looking only at the top of a long page.
• Ignoring mobile category strips, sidebars, or sticky elements.
• Treating a screenshot as clean without reading visible headings and CTA text.
• Forgetting to test the live mapped domain after a Cloud Run deploy.

Verification steps

• Capture screenshots for the home/index route and at least two changed pages.
• Measure horizontal overflow at the document level.
• Inspect a sample of image natural widths and heights.
• Run a broad search or filter query when the page has discovery features.
• Open the contact sheet and check for obvious spacing, crop, and duplicate-image mistakes.