qa-only

To generate a bug report without fixes, you can run a report-only QA pass. This systematically tests the web application and produces a structured report with a health score, screenshots, and reproducible steps while ensuring no code is modified.

A structured QA report for release verification includes an application health score, captured screenshots, logs, and detailed reproduction steps. This provides shareable evidence of regressions across multiple pages and states during your testing process.

Yes, you can use report-only QA for ad-hoc testing, regression checks, and release verification. It executes tests across multiple pages and states to gather evidence and present findings without performing any fixes or altering the application code.

Report-only QA strictly identifies and surfaces bugs with reproduction steps and a health score without modifying code. A full test-fix-verify loop goes further by applying code changes to resolve the identified defects before verifying the fixes.

You capture screenshots and reproducible steps by running a report-only QA pass using allowed tools to execute tests. The process automatically gathers evidence, attaches screenshots, and logs reproduction steps into a portable, shareable format.

Use a report-only QA pass when you need to verify a new build or highlight regressions without applying fixes. It is ideal when you want a concise, shareable bug report with a health score rather than an automated code modification workflow.