ops-browser-uat_skill

This skill automates browser-based user acceptance testing with Playwright MCP tools, logging in, navigating features, and capturing visual proof via

TypeScript

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill codyswanngt/lisa --skill ops-browser-uat

SKILL.md4.4 KB

Overview

This skill runs browser-based user acceptance tests using Playwright MCP tools to log into the app, navigate key flows, and capture visual proof with screenshots. It automates authentication, page walkthroughs, error overlay handling, and records console/network issues to produce a concise PASS/FAIL report. It is designed for quick verification of staging, dev, or production-like environments.

How this skill works

The skill loads Playwright browser tools, verifies the target frontend is reachable, and launches scripted scenarios that mirror the project's end-to-end fixtures and selectors. It reproduces the exact login flow (phone + OTP), dismisses development error overlays, navigates selected routes, captures screenshots at each verification point, and collects console messages and failed network requests. Results are summarized in a tabular report with step-level status, counts of PASS/FAIL, and any JS or API errors.

When to use it

Run a quick smoke-test after a deploy to confirm core flows work
Validate authentication and session handling in staging or dev
Capture visual proof for QA sign-off or regressions
Verify specific pages or user journeys via the custom scenario
Monitor for JavaScript errors or failed API calls during UAT

Best practices

Load the Playwright MCP browser tools before running scenarios
Confirm the frontend URL responds (curl) and localhost is running on port 8081 when applicable
Read the project's selectors and auth fixture to mirror exact testids and flow timing
Take screenshots at each verification point and include console/network captures
Use timeouts and waits from the project's constants to avoid flaky checks

Example use cases

smoke-test dev: full app walkthrough and screenshots for a recent deploy
login staging: run only the login flow and capture proof of successful sign-in
home-screen dev: verify each home section loads and collect screenshots
custom production /path: login then navigate to a specific route for targeted verification
player-detail dev: open the player detail page and validate content and network calls

FAQ

The skill runs a small DOM script to remove known error-overlay elements and presses Escape as a backup to dismiss overlays before continuing.

What evidence does the skill produce?

It produces screenshots at each step, a table of step/ action/ status/ notes, counts of PASS/FAIL, and lists of console errors and failed network requests.