← ClaudeAtlas

agent-qa-browser-regressionlisted

Use when verifying an existing browser journey with agent-qa against a running Spring Boot application. Covers target selection, scoped execution, run evidence, and memidex provenance while preserving backend tests and security contracts.
rrezartprebreza/spring-boot-skills · ★ 357 · AI & Automation · score 89
Install: claude install-skill rrezartprebreza/spring-boot-skills
# agent-qa Browser Regression [agent-qa](https://github.com/vostride/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 4 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](../testing-pyramid/SKILL.md). - 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 browse