webapp-testing
π―SkillWeb application testing skill using native Python Playwright scripts for verifying frontend functionality, debugging UI behavior, capturing screenshots, and viewing browser logs
Installation
npx skills add composiohq/awesome-claude-skills --skill webapp-testingRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/webapp-testingInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/webapp-testing/ - All projects
~/.claude/skills/webapp-testing/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View on GitHub β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.
Web Application Testing
To test local web applications, write native Python Playwright scripts.
Helper Scripts Available:
scripts/with_server.py- Manages server lifecycle (supports multiple servers)
Always run scripts with --help first to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.
Decision Tree: Choosing Your Approach
User task β Is it static HTML?
ββ Yes β Read HTML file directly to identify selectors
β ββ Success β Write Playwright script using selectors
β ββ Fails/Incomplete β Treat as dynamic (below)
β
ββ No (dynamic webapp) β Is the server already running?
ββ No β Run: python scripts/with_server.py --help
β Then use the helper + write simplified Playwright script
β
ββ Yes β Reconnaissance-then-action:
1. Navigate and wait for networkidle
2. Take screenshot or inspect DOM
3. Identify selectors from rendered state
4. Execute actions with discovered selectors
Example: Using with_server.py
To start a server, run --help first, then use the helper:
Single server:
python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
Multiple servers (e.g., backend + frontend):
python scripts/with_server.py \
--server "cd backend && python server.py" --port 3000 \
--server "cd frontend && npm run dev" --port 5173 \
-- python your_automation.py
To create an automation script, include only Playwright logic (servers are managed automatically):
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
page = browser.new_page()
page.goto('http://localhost:5173') # Server already running and ready
page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
# ... your automation logic
browser.close()
Reconnaissance-Then-Action Pattern
-
Inspect rendered DOM:
page.screenshot(path='/tmp/inspect.png', full_page=True) content = page.content() page.locator('button').all() -
Identify selectors from inspection results
-
Execute actions using discovered selectors
Common Pitfall
β Don't inspect the DOM before waiting for networkidle on dynamic apps
β
Do wait for page.wait_for_load_state('networkidle') before inspection
Best Practices
- Use bundled scripts as black boxes - To accomplish a task, consider whether one of the scripts available in
scripts/can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use--helpto see usage, then invoke directly. - Use
sync_playwright()for synchronous scripts - Always close the browser when done
- Use descriptive selectors:
text=,role=, CSS selectors, or IDs - Add appropriate waits:
page.wait_for_selector()orpage.wait_for_timeout()
Reference Files
- examples/ - Examples showing common patterns:
element_discovery.py- Discovering buttons, links, and inputs on a pagestatic_html_automation.py- Using file:// URLs for local HTMLconsole_logging.py- Capturing console logs during automation
More from this repository10
A Claude Code plugin that analyzes meeting notes and transcripts to extract key insights, action items, and decisions using Composio app integrations.
A Claude Code plugin from the Awesome Claude Skills collection that downloads videos from YouTube and other platforms for offline viewing, editing, or archival, with support for various formats and quality options.
A Claude Code plugin that assists in writing high-quality content by conducting research, adding citations, improving hooks, and providing section-by-section feedback.
A Claude Code plugin that automatically organizes and categorizes files in your workspace using Composio integrations, helping maintain a clean project structure.
A Claude Code plugin providing tools for creating elaborate, multi-component HTML artifacts using React, Tailwind CSS, and shadcn/ui in claude.ai.
A Claude Code skill that randomly selects winners from participant lists, spreadsheets, or Google Sheets for giveaways and contests using cryptographically secure randomness.
A Claude Code plugin that automates Zoho CRM workflows including lead management, contact updates, deal tracking, account operations, and custom module interactions through Composio integration.
A Claude Code plugin that enforces brand consistency by checking code and content against your brand guidelines using Composio integrations.
A pre-built workflow skill for automating Help Scout via Composio, enabling Claude to manage conversations, customers, mailboxes, and tags through structured tool sequences and parameter guidance.
A Claude Code plugin that automatically creates user-facing changelogs from git commits by analyzing commit history and transforming technical commits into customer-friendly release notes.