aie-web-testinglisted

Write and run automated browser tests for a web app using Playwright — smoke tests, critical user journeys (sign-up, login, contact/checkout forms), navigation, and console/network-error checks — then report pass/fail with screenshots and repro steps. Scaffolds Playwright if the project doesn't have it, uses resilient role/text selectors, and can wire tests into CI. Complements a manual QA pass with real automation. Works with any stack the browser can load (React, Next.js, Vue, Svelte, plain HTML, WordPress). Trigger on "write tests for my site," "add Playwright tests," "test this user flow," "end-to-end tests," "e2e," "browser tests," "test my signup/checkout," or "set up automated testing."
mrhinkle/aienterprise-skills · ★ 2 · Web & Frontend · score 68

Install: claude install-skill mrhinkle/aienterprise-skills

# Web Testing (Playwright) One job: catch broken user journeys automatically. Write tests that mirror what real visitors do, run them, and report what failed with enough detail to fix it. Automation to back up — not replace — a human QA pass (`aie-web-qa`). Read `reference/setup.md` to install/configure, `reference/patterns.md` before writing tests, and `reference/reporting.md` for the output shape. ## Safety & scope - Test against **local dev, staging, or sites the person owns/authorizes** — never someone else's production. Confirm the target before running. - Tests are **read-only against the app's UI**. Do not create test flows that send real money, real emails to third parties, or real irreversible actions against production. Use test/staging data. - Never hardcode real credentials or secrets in test files — read them from environment variables. Treat any secret you see as sensitive. ## The loop: Discover → Set up → Write → Run → Triage → Report ### 1. Discover Identify the **critical journeys** — the handful of flows that, if broken, cost the business. Typical: load the homepage, primary navigation, sign-up, log in, the main form (contact / lead / checkout), search, and one core "money" path. Ask for or infer the base URL and any test accounts. See `reference/patterns.md` for how to choose journeys. ### 2. Set up If the project has no Playwright, scaffold it (`npm init playwright@latest` or add `@playwright/test` + `npx playwright install`). Add a `playwright.confi