Web App Testing
A toolkit for testing local web applications with Playwright: verify frontend behavior, debug UI problems, capture screenshots and read browser logs.
이 리소스는 영어로만 제공됩니다.
이 스킬을 사용할 때
- Use when you need to verify or debug a locally running web UI.
- Use when you want screenshots or browser console logs as evidence.
가져오는 방법
- Open the source folder linked above (
skills/webapp-testingin the anthropics/skills repository). - Copy the whole folder, not just SKILL.md: a skill can include scripts, references and assets that SKILL.md relies on.
- Place it where your agent loads skills. For Claude Code this is
.claude/skills/webapp-testing/in a project or~/.claude/skills/webapp-testing/for all projects (see the Claude Code skills documentation). - Read SKILL.md and any scripts before enabling them: KitLocal does not install skills or run their scripts.
스킬은 폴더입니다. SKILL.md만 복사하면 의존하는 파일이 빠질 수 있습니다. KitLocal은 스킬을 설치하거나 스크립트를 실행하지 않습니다. 먼저 내용을 검토하세요.
SKILL.md (소스에서 가져와 텍스트로 표시)
---
name: webapp-testing
description: 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.
license: Complete terms in LICENSE.txt
---
# 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:**
```bash
python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
```
**Multiple servers (e.g., backend + frontend):**
```bash
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):
```python
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
1. **Inspect rendered DOM**:
```python
page.screenshot(path='/tmp/inspect.png', full_page=True)
content = page.content()
page.locator('button').all()
```
2. **Identify selectors** from inspection results
3. **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 `--help` to 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()` or `page.wait_for_timeout()`
## Reference Files
- **examples/** - Examples showing common patterns:
- `element_discovery.py` - Discovering buttons, links, and inputs on a page
- `static_html_automation.py` - Using file:// URLs for local HTML
- `console_logging.py` - Capturing console logs during automation관련 리소스
MCP 서버
Playwright MCPBrowser automation for AI assistants through Playwright: navigate pages, interact with elements and read page state.
엄선 + 실시간Microsoft · v0.0.857일 전 업데이트
playwrightbrowserautomationtesting
이 카탈로그 정보
내장 스냅샷 · 2026. 11. 15. 오전 6:05에 게시됨 · 카탈로그 리비전 5bc079fe355af2214bc0
앱에 내장된 스냅샷을 표시하고 있습니다(콘텐츠 소스가 설정되지 않았습니다). 소스에는 더 새로운 콘텐츠가 있을 수 있습니다.