qa-only

To generate a QA report with screenshots and reproduction steps, you can run a report-only QA pass against your web application. This process produces a structured health report that systematically documents bugs without applying any source code fixes.

Report-only QA testing is the process of systematically evaluating a web application to document bugs and generate a quality report without applying fixes. You need it when you want to document issues for audits or when a complete fix loop is not desired.

You can document bugs without modifying source code by running a report-only QA testing pass. This approach uses task orchestration to formally evaluate the web application and output a structured quality report with reproduction steps and evidence.

Yes, report-only QA testing provides a formal health score for your web application. The structured QA report includes this score alongside captured screenshots and detailed reproduction steps to give you a clear quality assessment.

Yes, you can use this QA report approach when you want to document issues without fixing them. It is specifically designed for scenarios where you ask to just report bugs, ensuring documentation rather than changes to the source code.

The main limitation of report-only QA testing is that it strictly generates documentation and does not modify source code. It outputs a structured health report with reproduction steps but cannot be used to apply fixes or resolve the discovered bugs.