admin-asset-e2e

Automate admin asset and vulnerability E2E testing by spinning up backend and frontend services with Gradle and npm, then executing Playwright tests to verify admin workflows and normal user visibility across the running stack.

Playwright E2E tests often fail due to service startup timing or health check issues. This Skill addresses intermittent failures by performing iterative fixes with health checks and restart logic until tests pass or the budget is exhausted.

Verify normal user visibility of admin-added vulnerabilities in a CI-CD pipeline by orchestrating an E2E test suite that creates an asset, assigns ownership, adds a vulnerability, and confirms visibility from a normal user perspective.

Yes, you can use Gradle and npm to spin up backend and frontend services for Playwright E2E testing. The orchestration starts the required stack, runs the tests, and performs iterative failure analysis to ensure a green test state.

Yes, the E2E testing approach supports iterative failure fixes without manual intervention by running a retry loop that analyzes failures, applies fixes, and performs health checks and restarts until all tests pass or the budget is exhausted.

You need automated QA orchestration for admin asset and vulnerability workflows when QA or DevOps teams must repeatedly verify that an admin can create a system, assign ownership, and add a vulnerability across a running full-stack environment.