qa-only

To generate a report-only QA assessment, you can run a non-fix testing process that validates UI flows and API responses. This produces a structured health check report with screenshots and repro steps while avoiding any source code modifications.

Report-only QA testing systematically evaluates a web application to produce a structured health snapshot without deploying fixes. Use it for build validation, regression checks, or exploratory testing when stakeholders need an objective bug report rather than code changes.

To capture screenshots and reproducible steps during bug reporting, run an automated evidence-collection process during web app testing. This generates a formal QA report documenting each failure with visual proof and exact replication steps.

Yes, you can run regression checks without modifying the repository by using a non-fix testing approach. It validates state transitions and UI flows against the current build and outputs a transparent health score narrative instead of applying patches.

Report-only testing works for both UI flows and API responses by executing automated test steps across the web application. It systematically checks these layers and compiles findings into a formal QA report without altering the deployment.

You should avoid a non-fix QA testing approach when your workflow requires the testing tool to also resolve the identified bugs. If you need a complete test-fix-verify loop that modifies source code, use a full QA automation skill instead.