qa-only

Bug report generation for web app regression testing automates structured QA passes to collect reproducible steps, health scores, and evidence like screenshots without applying code changes. This preserves the current application state for thorough defect triage.

Report-only QA testing identifies and documents defects in a web application without applying patches. You need it for post-release regression checks and defect triage when testers must surface high-priority issues for engineering review without modifying source code.

Manual QA checks can systematically capture screenshots and document defects without modifying source code. The process attaches artifacts and summarizes issues while preserving the current application state for later verification.

The best way to perform a sanity check that surfaces high-priority issues is to run an automated report-only QA pass. It systematically collects health metrics and evidence, summarizing issues for engineering review without applying any patches.

A testing harness is required to collect health metrics, reproduce steps, and attach artifacts during a QA pass. The harness integration enables the systematic collection of evidence needed to generate structured bug reports.

This QA testing approach does not apply patches or fix code during bug triage to preserve the current application state. It focuses entirely on documenting defects with reproducible steps and evidence so fixes can be verified later.