full-stack-test-gatelisted

Test a whole application and prove it works, gated by checks that actually run — the project's own unit/integration/regression suites, then a real browser that boots the app, clicks through every feature flow, screenshots each step, and fails on console errors, uncaught exceptions or failed requests; plus pixel-level visual regression and a crawler that reports which features no test touches. Use when the user wants to test an app end to end, write or run unit / integration / regression tests, set up E2E or Playwright testing, drive the UI and take screenshots, verify a change didn't break anything, add a test gate to CI, or find out what is untested. Triggers: "test the app", "end-to-end", "e2e", "regression test", "unit tests", "Playwright", "screenshot the UI", "click through the app", "smoke test", "QA", "visual regression", "test all features", "does it still work".
NeuralMedic-DE/claude-skills · ★ 0 · Testing & QA · score 73

Install: claude install-skill NeuralMedic-DE/claude-skills

# Full-stack test gate (unit → e2e, verified) Prove an application works by **running it**: the project's own test suites, then a real browser that boots the app, drives every feature, screenshots each step, diffs the pixels, and names what nothing tested. ## Core principle **"It works" is a claim; a green gate is evidence — and evidence has a scope.** The loop is: run the suites → drive the flows → diff the screenshots → crawl for what no flow touches → fix → re-run. **Be honest about scope (the rule that keeps this skill correct):** a green run means *the flows you wrote passed*. It does not mean the app works. Never report "fully tested" or "all features work". Report **"N flows green, M% of controls untouched by any flow"** — and the crawler exists precisely to produce that second number. → `references/01-test-strategy-and-scope.md` ## When to use vs. not - Use for: testing a web app end to end; writing/running unit, integration or regression tests; setting up Playwright; driving the UI and screenshotting it; visual regression; verifying a change didn't break anything; adding a test gate to CI; finding out what is untested. - Not for: load/performance testing, security testing, or native mobile apps (different tooling). For accessibility, use the sibling `a11y-gate` skill. ## Inputs to gather first 1. **How to start the app** — the command and the URL. Prefer the **production build** (`npm run build && npm run preview`); dev servers add overlays and