qa-only

To generate a QA report, trigger the report-only workflow to navigate pages via Playwright CLI, capture screenshots, and document reproducible steps without applying code fixes. It outputs structured health reports across feature branches, staging, and CI pipelines.

Non-intrusive QA testing works by enforcing guardrails that restrict the workflow to identifying and documenting symptoms. It uses browser-based navigation to validate application quality and deliver structured reports without making changes to the codebase.

Yes, you can use Playwright CLI within CI pipelines to capture screenshots and document bugs. The workflow supports feature branches and staging environments, enabling fast validation and structured reporting without code modifications.

The best way to run diff-aware QA checks is to trigger the QA workflow in your project workspace. It supports diff-aware and quick modes to validate feature branches fast, producing a structured health report with screenshots and repro steps.

Yes, report-only QA testing supports quick mode for fast validation. This mode works alongside diff-aware checks to quickly navigate pages and document issues, delivering a structured QA report without applying fixes to the codebase.

You should not use a report-only approach when your goal is to automatically apply fixes to the codebase. This workflow enforces guardrails to strictly identify and document web application issues, meaning no code changes are made during the testing process.