Web app testing with Playwright scripts
Tests a local web app with Python Playwright scripts: a helper starts and stops the servers, the agent inspects the rendered page, then clicks, fills, takes screenshots and reads console logs. Use when checking a frontend change or reproducing a UI bug.
webapp-testing- Author
- Anthropic
- Source
- anthropics/skills/skills/webapp-testing @ e4bb5d9
- License
- Apache-2.0 · Copyright 2026 Anthropic, PBC.
About this skill
What it does
The skill has the agent test a local web app by writing small Python Playwright scripts (sync API, headless Chromium). A decision tree picks the approach. A static HTML file is read for selectors and opened through file://. A dynamic app gets "reconnaissance, then action": open the page, wait for networkidle, take a screenshot or dump the DOM, take selectors from what actually rendered, then click and fill. Inspecting before networkidle is the pitfall the skill warns about.
scripts/with_server.py runs the servers the app needs. It starts one or several commands, waits until each port accepts connections (30 seconds by default, --timeout), runs your script and stops the servers, so the Playwright script holds only browser logic. The agent calls it with --help and treats it as a black box. examples/ has three patterns: element_discovery.py lists buttons, links and inputs, static_html_automation.py fills a form in a local file, console_logging.py collects console messages. They save to /tmp/ and /mnt/user-data/outputs/, paths from Anthropic's sandbox; change them on your machine.
You need Python with the playwright package and its Chromium; the skill does not cover installing them.
When to use it, and when not
Use it to check that a frontend change works, reproduce a UI bug, take screenshots or read console errors in an app you can run locally.
It leaves throwaway scripts, not a test suite: no @playwright/test specs, nothing for CI.
How to run it
The install command below puts the whole folder in place. The agent picks the skill up when a UI needs checking; to call it yourself:
- Claude Code:
/webapp-testing, or ask for the skill by name. - Codex:
$webapp-testing. - Cursor: type
/in the Agent chat and pickwebapp-testing.
Example: /webapp-testing Start the app with npm run dev on port 5173, log in as the demo user and check that the dashboard loads without console errors.
How it differs from similar skills
E2E tests with Playwright from our catalog writes @playwright/test specs that stay in the repository and run in CI. Browser automation with Playwright CLI drives the browser with playwright-cli commands and element refs from page snapshots, without writing scripts; it needs Node and npx. Browser testing with Chrome DevTools MCP inspects a live Chrome through an MCP server. This skill is one Python script per check plus a helper for the servers.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/webapp-testing/SKILL.md https://anymodel.org/en/skills/anthropic/webapp-testing/SKILL.md -o ~/.claude/skills/webapp-testing/LICENSE.txt https://anymodel.org/en/skills/anthropic/webapp-testing/LICENSE.txt -o ~/.claude/skills/webapp-testing/examples/console_logging.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/console_logging.py -o ~/.claude/skills/webapp-testing/examples/element_discovery.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/element_discovery.py -o ~/.claude/skills/webapp-testing/examples/static_html_automation.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/static_html_automation.py -o ~/.claude/skills/webapp-testing/scripts/with_server.py https://anymodel.org/en/skills/anthropic/webapp-testing/scripts/with_server.py && chmod +x ~/.claude/skills/webapp-testing/scripts/with_server.py
curl -fsSL --create-dirs -o ~/.agents/skills/webapp-testing/SKILL.md https://anymodel.org/en/skills/anthropic/webapp-testing/SKILL.md -o ~/.agents/skills/webapp-testing/LICENSE.txt https://anymodel.org/en/skills/anthropic/webapp-testing/LICENSE.txt -o ~/.agents/skills/webapp-testing/examples/console_logging.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/console_logging.py -o ~/.agents/skills/webapp-testing/examples/element_discovery.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/element_discovery.py -o ~/.agents/skills/webapp-testing/examples/static_html_automation.py https://anymodel.org/en/skills/anthropic/webapp-testing/examples/static_html_automation.py -o ~/.agents/skills/webapp-testing/scripts/with_server.py https://anymodel.org/en/skills/anthropic/webapp-testing/scripts/with_server.py && chmod +x ~/.agents/skills/webapp-testing/scripts/with_server.py
foreach ($f in 'SKILL.md','LICENSE.txt','examples/console_logging.py','examples/element_discovery.py','examples/static_html_automation.py','scripts/with_server.py') { $p = Join-Path "$HOME\.claude\skills\webapp-testing" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/anthropic/webapp-testing/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','LICENSE.txt','examples/console_logging.py','examples/element_discovery.py','examples/static_html_automation.py','scripts/with_server.py') { $p = Join-Path "$HOME\.agents\skills\webapp-testing" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/anthropic/webapp-testing/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/anthropic/webapp-testing/SKILL.md
SKILL.md
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
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel