qa-only

Generate a structured bug report for a web application by running a report-only QA testing pass that enforces no code changes, focusing solely on documentation-style outputs like health scores, screenshots, and reproducibility steps.

Report-only QA testing is a non-fixing verification pass on a new build that systematically tests a web application and produces a structured report with a health score, screenshots, and repro steps. Use it when you want to just report bugs without applying fixes.

Yes, you can run a QA health check without a live environment. This report-only testing process is designed to work with or without live environments, returning a comprehensive, review-ready bug report with evidence collection.

The best way to document bug reproducibility steps and capture screenshots is to use a systematic QA testing process that automatically collects evidence, calculates a health score, and compiles everything into a review-ready structured bug report.

Report-only QA focuses exclusively on documentation and evidence collection, enforcing no code changes to produce a structured bug report. A full test-fix-verify loop actively fixes identified issues, requiring a different testing approach.

Yes, a report-only QA pass includes a health score for the tested web application. The resulting structured bug report combines this health score with screenshots and reproducibility steps to provide a comprehensive overview of build quality.