qa-only

To generate a structured QA report without applying fixes, you can use a non-destructive testing workflow that identifies defects and outputs health scores, screenshots, and reproducible steps. This ensures end-to-end test documentation without modifying the application.

A non-destructive QA testing workflow for pre-release cycles includes manual exploratory testing and automated QA workflows, evidence capture like screenshots, credential redaction in reports, and structured documentation of reproducible steps.

Yes, you can use this QA reporting approach for both automated QA workflows and manual exploratory testing. It systematically identifies defects in development, staging, and pre-release environments to validate new builds.

The best way to report bugs without changing code is to use a report-only QA testing process that captures evidence and generates a health score. This delivers consolidated findings to stakeholders while keeping the application untouched.

You should use a report-only QA test when asked to just report bugs or test but don't fix. If you need the full test-fix-verify loop where defects are automatically resolved, you should use a different automated QA workflow.