qa-only

Automated QA testing without code modification is achieved by running non-destructive end-to-end simulations on your web application. The Skill executes user journeys like form submissions, captures evidence, and generates a structured health report without applying any fixes.

Yes, you can generate evidence-rich QA reports that include health scores, screenshots, and explicit reproducible steps. These reports are exported to a dedicated .gstack/qa-reports directory, providing structured evidence for each finding during bug hunts or QA sign-offs.

Non-destructive QA testing means the process simulates user interactions across dynamic states and critical flows but never applies fixes to the application. It strictly surfaces issues and documents them with screenshots and reproducible steps in a structured health report.

Yes, the QA testing workflow covers end-to-end user journeys including login flows, form submissions, and critical application paths. It automates these interactions to surface issues and exports the findings into a structured health report.

The best way to surface web application issues for QA sign-off is to automate a full QA pass that simulates common user journeys. This process generates a structured health report complete with health scores, screenshots, and reproducible steps without altering the code.

The primary limitation is its non-fixing workflow; the automated QA testing strictly surfaces issues and generates structured reports with reproducible steps. It never applies fixes to the code, meaning developers must address the findings separately.