qa-only

Automated QA testing can explore pages, click elements, and collect a structured report without applying fixes. This approach generates reproducible findings, evidence-backed health scores, and screenshots across multiple pages and states while keeping your source code intact.

Yes, automated bug reporting can run on a feature branch to verify that new UI changes don't introduce obvious regressions. It systematically explores interactions and states to generate a defect report, ensuring your deployment environment remains unchanged.

To start automated QA testing, you need to provide a target URL or have a detected local app. The testing process uses this entry point to explore pages and collect evidence-backed health scores and screenshots.

Automated QA testing supports both diff-aware and full-mode testing for web applications. Diff-aware testing focuses on verifying specific changes, while full-mode testing performs a thorough exploration of all pages and states to generate a comprehensive report.

An automated QA defect report includes reproducible findings, evidence-backed health scores, screenshots, and repro steps. It systematically documents defects discovered while exploring pages, interactions, and states across the target web application.

You should not use report-only automated QA testing when you need to automatically fix bugs or modify source code. This approach is strictly designed for uncovering bugs and generating structured reports without making changes to the environment or deployment.