08-REVIEW-clickthrough

A clickthrough QA test simulates real user interactions in a headed browser to identify console errors, server errors, i18n failures, and UI bugs. This Skill automates that process by capturing interactive elements, state changes, and form validation issues, then generating a detailed findings report with screenshots.

Headed-browser UI testing launches a visible browser session to manually or automatically verify feature workflows. You need it after developing a new feature to ensure all buttons, forms, and navigation work as expected and to catch visual or functional defects before release.

Yes, this tool captures form validation issues and documents every interactive element and state change during the clickthrough. It simulates real user interactions to verify that forms, buttons, and navigation transitions behave correctly across the feature's UI.

The best way to document UI bugs is to generate a structured FINDINGS.md report with bug classifications and screenshots. This Skill automatically compiles all detected console errors, server errors, and UI defects into that format, providing a thorough record for the development team.

No external dependencies are required to run this UI clickthrough test. The Skill operates independently using its built-in scripts and references to execute the headed-browser session, capture errors, and generate the findings report without additional setup.