What problem does it solve?
Turning local web app behavior into reliable, repeatable tests is hard, especially when UIs are dynamic and require careful synchronization and selector discovery.
Core Features & Use Cases
- Headless Playwright automation: Drive Chromium to validate UI behavior for local pages.
- Server lifecycle helper: Use
scripts/with_server.py to reliably start/stop one or more local servers while tests run.
- Reconnaissance-then-action workflow: Screenshot/inspect rendered DOM after waiting for
networkidle, then write actions using discovered selectors.
Example use case: Validate that a login page displays expected elements, fills fields correctly, submits the form, and produces the expected post-login UI state—by waiting for dynamic rendering, capturing screenshots for debugging, and using stable selectors.
Quick Start
Ask an agent to use the webapp-testing skill to automate your local app by running the helper script with --help to confirm parameters, then writing a minimal Playwright script that navigates to your running app, waits for network idle, and performs UI assertions/actions with discovered selectors.