qa-only

You can run report-only QA testing to systematically explore web app pages and interactions, generating a structured defect report with health scores and reproducible steps without applying fixes.

An automated web app defect report includes health scores, annotated screenshots, and step-by-step reproducible steps for identified bugs, providing structured documentation of defects found during systematic page exploration.

Yes, a browser automation environment is required to drive tests and assemble the final QA report. You also need access to the target URL and allowed tools like Bash, Read, Write, and AskUserQuestion to execute the testing process.

Use exploratory QA testing for quick sanity checks, regression verification, or when you need bug reports without code changes. It is ideal for evaluating application health and documenting defects before committing to modifications.

Yes, report-only QA is ideal for regression verification on web apps. It systematically evaluates interactions to confirm existing functionality, delivering a defect report with health scores and reproducible steps without modifying the underlying code.

The primary limitation is that report-only QA testing never applies fixes or modifies code; it strictly generates defect reports. Users must separately implement any code changes based on the provided bug reports and reproducible steps.