Agent skill · software engineering · github
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Why this skill is useful
Provides specific Playwright commands and patterns for testing web applications that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Web Application Testing This skill enables comprehensive testing and debugging of local web applications using Playwright automation. You should use the Playwright MCP Server to undertake the work if possible. If the MCP Server is unavailable, you can run the code in a local Node.js environment with Playwright installed. When to Use This Skill Use this skill when you need to: Test frontend functionality in a real browser Verify UI behavior and interactions Debug web application issues Capture screenshots for documentation or debugging Inspect browser console logs Validate form submissions and user flows Check responsive design across viewports Prerequisites Node.js installed on the system A locally running web application (or accessible URL) Playwright will be installed automatically if not present Core Capabilities 1. Browser Automation Navigate to URLs Click buttons and links Fill form fields Select dropdowns Handle dialogs and alerts 2. Verification Assert element presence Verify text content Check element visibility Validate URLs Test responsive behavior 3. Debugging Capture screenshots View console logs Inspect network requests Debug failed tests Usage Examples Example 1: Basic Navigation Test Example 2: Form Interaction Example 3: Screenshot Capture Guidelines 1. Always verify the app is running - Check that the local server is accessible before running tests 2. Use explicit waits - Wait for elements or navigation to complete before interacting 3. Capture screenshots on failure - Take screenshots to help debug issues 4. Clean up resources - Always close the browser when done 5. Handle timeouts gracefully - Set reasonable timeouts for slow operations 6. Test incrementally - Start with simple interactions before complex flows 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/webapp-testing