web-app-testing
/web-app-testing
Test a local web application through realistic browser interactions. Use when validating user journeys, forms, navigation, responsive behavior, or UI regressions in a running development app.
- Author
- voyager67 ↗
- Repository
- Agent-Workbench ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Test a local web application through realistic browser interactions. Use when validating user journeys, forms, navigation, responsive behavior, or UI regressions in a running development app.
Original author description
Test a local web application through realistic browser interactions. Use when validating user journeys, forms, navigation, responsive behavior, or UI regressions in a running development app.
How it works
SKILL.md has no level-two headings · 16 lines, 234 words
SKILL.md preview
--- name: web-app-testing description: Test a local web application through realistic browser interactions. Use when validating user journeys, forms, navigation, responsive behavior, or UI regressions in a running development app. --- # Web App Testing Test behavior from the user's perspective, using the project's existing browser-test stack where possible. 1. Inspect the repository, app start command, existing test framework, routes, fixtures, and current browser-test conventions before adding tooling. 2. Confirm the target is a local or approved test environment. Never point an automated test at production or real customer data without explicit authorization. 3. Choose a small set of critical user journeys and acceptance criteria. Include success, validation, empty, loading, and failure states where relevant. 4. Prefer accessible locators (role, label, text) over brittle CSS selectors or positional assumptions. Use stable test IDs only when semantic selectors are not sufficient. 5. Make tests deterministic with isolated fixtures, controlled network responses, known state, and cleanup. Avoid arbitrary sleeps; wait for observable conditions. 6. Cover keyboard interaction and essential viewport sizes when they are material to the feature. Check console errors and failed requests for relevant regressions. 7. Capture screenshots, traces, or videos only when they help diagnose a failure. Protect credentials, tokens, and personal information in artifacts. 8. Run the focused tests, then the relevant suite. Report exact commands, browser/runtime, pass/fail state, flaky behavior, and scenarios not covered. Do not change application behavior merely to satisfy a brittle test. Do not claim visual or accessibility certification from a small smoke test. If the browser tooling is unavailable, state that limit and use the strongest safe alternative.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · voyager67/Agent-Workbench | 86 | MIT |
| paulocoutinhox/skills | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
Database snapshot: 13.11.2026 · package version 48c38fbab60b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90release-qa
Test an AI-built web app like a senior QA engineer before release. Use when the user asks to test, QA, verify, ship, check regressions, inspect a browser flow, or decide whether a web app is ready to launch. - 100d3k
Test and debug a web app in its existing d3k browser, including local Chrome connected to a Vercel Sandbox over CDP. Use for UI checks, browser interactions, screenshots, and reproducing app issues when d3k is running. - 100web-app-qa
Systematic exploratory testing of a running web app in a real browser - smoke checks, feature-by-feature exploration, responsive and accessibility passes - with reproducible evidence for every finding (repro steps, screenshots, video, severity) and a ship verdict. Use to QA,… - 100web-debug
You MUST use this when interacting with or testing local web applications with Playwright - verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs. - 100agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages. - 90uds-web-development
Use when building or maintaining website or web-application routes, pages, forms, browser behavior, rendering, responsive layouts, or required PWA and Mini App features.