agent-qa Browser Regression

agent-qa by vostride executes natural-language app tests. Its advanced memidex memory engine and self-improvement capabilities help reuse experience across runs. Use it for a small set of browser-visible journeys alongside this project's unit, slice, and integration tests.

This is the Spring Boot 3 variant. The external browser workflow is the same for Boot 3 and 4; keep the application's existing Java, Spring, security, and test dependencies. agent-qa runs separately on Node.js 24+, not as a Maven dependency. An API-only service without a browser UI should use the existing HTTP/integration testing skills instead.

Conventions

• Start with the project's own build/test and application-start commands. Keep existing verification gates; do not replace MockMvc, repository tests, or Testcontainers with browser coverage. See testing-pyramid.
• Identify the actual UI origin, application build, target, and test fixture. A separate frontend, reverse proxy, API port, and Actuator management port are different surfaces. A successful health check is readiness evidence, not a passing user journey. Keep a random-port server alive for the browser run and use its actual reachable origin.
• Preserve authentication, authorization, CSRF, tenant boundaries, response envelopes, and routes. Use a limited test account and the app's existing login path; do not disable security to make the browser pass. Check that fixtures belong to a disposable or explicitly approved test environment. Server-side writes made through real HTTP do not roll back with a test thread's transaction: use the project's scoped cleanup mechanism for records this run owns.
• Work from the directory containing agent-qa.config.yaml, with an already installed agent-qa CLI. Confirm Node.js, browser/provider availability, and the selected test's target before execution. Use the installed command or npx --no-install agent-qa; check --help for the installed version.
• Keep credentials in the configured workspace.secretsFile; test steps reference {{secret:NAME}}. Avoid literal credentials in CLI arguments, test files, screenshots, or published reports. Review image/video artifacts before sharing; text masking does not cover all sensitive content.
• Review existing tests before running them. If a new test is needed, use agent-qa's supported authoring workflow so it supplies stable IDs; preserve those IDs and the original assertions. A natural-language test can mutate the app. Run only the selected, authorized journey; production execution needs explicit authorization and the documented configuration gate, never a casual bypass.

Scoped execution and evidence

For an existing checkout test, after environment and scope are confirmed: