gstack-qa-only

To generate a bug report without code fixes, you can request a report-only QA run that produces a structured deliverable with health scores, screenshots, and step-by-step reproduction data while strictly avoiding any modifications to the application code.

Report-only QA testing is the process of running systematic checks on a web application to capture its health score and reproduction steps without implementing fixes. It is needed for bug triage and validation scenarios where you require confirmation and evidence rather than code changes.

Yes, you can get a health score and screenshots for bug triage without modifying the codebase by requesting a deterministic, report-only QA execution that focuses on health assessment and visual evidence capture while preventing any code alterations.

The best way to document step-by-step reproduction steps is to use a report-only QA workflow that systematically captures precise repro data and screenshots in a structured bug-report format, ensuring clear validation evidence without attempting to fix the underlying issues.

Report-only QA differs from a full fix-and-verify workflow by strictly separating bug documentation from code changes. It focuses on generating health scores, screenshots, and repro steps, whereas a full workflow routes to a fix-and-verify process that modifies the application.

You should not use a report-only approach when you need automated code fixes or a fix-and-verify testing loop. This method is constrained to bug triage, health assessment, and evidence collection, intentionally avoiding any code modifications or issue resolutions.