App Testing
Public Made by Adomby adom
Build a browser-driven end-to-end test suite that RENDERS your web app in real Chrome, clicks every control, fails on any page error, and gates on interaction coverage so a new untested button turns the suite red.
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install adom/app-testingBuild and maintain a browser-driven end-to-end test suite for a web app that actually RENDERS the page in real Chrome, clicks every control, and fails on any page error — plus an interaction-coverage gate that fails when a NEW control ships without a test. Use when the user asks to test a web UI, add UI/E2E tests, "click through every button", verify every control works, catch UI regressions, set up Puppeteer/pup tests, or asks "why did the tests pass while the app was broken". Covers the harness (self-hosted server + seeded state + in-container Chrome), the page-error gate, the control-coverage manifest, viewport matrix, and the pitfalls that make UI tests lie. Trigger words: test the app, UI test, E2E test, end-to-end test, functional test, click every button, interaction coverage, coverage gate, puppeteer test, pup test, catch UI regression, headless chrome test, assert behavior not placement, control walk, test suite.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.