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. Activate on: Playwright, webapp testing, browser automation, E2E testing, UI testing. NOT for API-only testing without browser, unit tests, or mobile app testing.
Best use case
webapp-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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. Activate on: Playwright, webapp testing, browser automation, E2E testing, UI testing. NOT for API-only testing without browser, unit tests, or mobile app testing.
Teams using webapp-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/webapp-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How webapp-testing Compares
| Feature / Agent | webapp-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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. Activate on: Playwright, webapp testing, browser automation, E2E testing, UI testing. NOT for API-only testing without browser, unit tests, or mobile app testing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Web Application Testing
Write native Python Playwright scripts to test local web applications.
## When to Use
✅ **Use for:**
- E2E testing of web applications
- UI automation and interaction testing
- Visual regression testing
- Browser log capture and debugging
- Screenshot capture for verification
- Form submission and validation testing
❌ **NOT for:**
- API-only testing without a browser (use requests/httpx)
- Unit testing of individual functions
- Mobile app testing (use Appium)
- Load/performance testing (use k6/Locust)
## 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 → Start server first, then run Playwright
│
└─ 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
```
## Core Playwright Patterns
### Basic Test Structure
```python
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True) # Always headless
page = browser.new_page()
page.goto('http://localhost:5173')
page.wait_for_load_state('networkidle') # CRITICAL for SPAs
# ... your test logic
browser.close()
```
### Reconnaissance-Then-Action Pattern
**Step 1: Inspect rendered DOM**
```python
page.screenshot(path='/tmp/inspect.png', full_page=True)
content = page.content()
buttons = page.locator('button').all()
```
**Step 2: Identify selectors** from inspection results
**Step 3: Execute actions** using discovered selectors
## Selector Strategy (Priority Order)
1. **Role-based** (best for accessibility):
```python
page.get_by_role("button", name="Submit")
page.get_by_role("textbox", name="Email")
```
2. **Text-based** (readable, but fragile to copy changes):
```python
page.get_by_text("Sign In")
page.get_by_label("Password")
```
3. **Test IDs** (stable, explicit):
```python
page.get_by_test_id("login-button")
```
4. **CSS selectors** (last resort):
```python
page.locator(".btn-primary")
page.locator("#submit-form")
```
## Common Anti-Patterns
### Anti-Pattern: Not Waiting for Network Idle
**Symptom**: Tests pass locally, fail in CI; elements not found
**Problem**: Modern SPAs load content dynamically after initial page load
**Solution**:
```python
# ❌ Wrong
page.goto('http://localhost:3000')
page.click('button') # Element may not exist yet
# ✅ Correct
page.goto('http://localhost:3000')
page.wait_for_load_state('networkidle')
page.click('button')
```
### Anti-Pattern: Hardcoded Waits
**Symptom**: `time.sleep(3)` scattered throughout tests
**Problem**: Slow, unreliable, doesn't adapt to actual page state
**Solution**:
```python
# ❌ Wrong
time.sleep(5)
page.click('.dynamic-button')
# ✅ Correct
page.wait_for_selector('.dynamic-button', state='visible')
page.click('.dynamic-button')
```
### Anti-Pattern: Inspecting DOM Before JavaScript Executes
**Symptom**: Empty page content, missing elements in static analysis
**Problem**: Reading HTML before client-side rendering completes
**Solution**: Always wait for `networkidle` on dynamic apps before inspection
## Waiting Strategies
```python
# Wait for element to appear
page.wait_for_selector('#my-element')
# Wait for element to be visible
page.wait_for_selector('#my-element', state='visible')
# Wait for element to be hidden
page.wait_for_selector('#my-element', state='hidden')
# Wait for navigation
page.wait_for_url('**/dashboard')
# Wait for network idle (all requests complete)
page.wait_for_load_state('networkidle')
# Custom wait with timeout
page.wait_for_function('document.querySelector(".loaded")')
```
## Screenshot Patterns
```python
# Full page screenshot
page.screenshot(path='/tmp/full.png', full_page=True)
# Element screenshot
page.locator('#header').screenshot(path='/tmp/header.png')
# Before/after comparison
page.screenshot(path='/tmp/before.png')
# ... perform action ...
page.screenshot(path='/tmp/after.png')
```
## Console Log Capture
```python
# Capture all console messages
messages = []
page.on('console', lambda msg: messages.append({
'type': msg.type,
'text': msg.text
}))
# Filter errors only
page.on('console', lambda msg:
print(f'ERROR: {msg.text}') if msg.type == 'error' else None
)
```
## Form Testing
```python
# Fill form fields
page.fill('#email', 'test@example.com')
page.fill('#password', 'secret123')
# Select dropdown
page.select_option('#country', 'US')
# Check checkbox
page.check('#terms')
# Submit form
page.click('button[type="submit"]')
# Verify submission
page.wait_for_url('**/success')
```
## Assertions
```python
from playwright.sync_api import expect
# Element assertions
expect(page.locator('#title')).to_have_text('Welcome')
expect(page.locator('#count')).to_have_text('5')
expect(page.locator('.error')).to_be_hidden()
expect(page.locator('#submit')).to_be_enabled()
# Page assertions
expect(page).to_have_url('http://localhost:3000/dashboard')
expect(page).to_have_title('My App')
```
## Multi-Page Scenarios
```python
# Handle popup windows
with page.expect_popup() as popup_info:
page.click('#open-popup')
popup = popup_info.value
popup.wait_for_load_state()
# Handle new tabs
with context.expect_page() as new_page_info:
page.click('a[target="_blank"]')
new_page = new_page_info.value
```
## Test File Organization
```
tests/
├── conftest.py # Shared fixtures
├── test_login.py # Login flows
├── test_dashboard.py # Dashboard features
├── test_forms.py # Form submissions
└── screenshots/ # Visual artifacts
```
## Running Tests
```bash
# Run single test file
python -m pytest tests/test_login.py
# Run with browser visible (debugging)
PWDEBUG=1 python -m pytest tests/test_login.py
# Generate trace for debugging
python -m pytest --tracing=on tests/test_login.py
```
## Best Practices
1. **Use `sync_playwright()`** for synchronous scripts
2. **Always close the browser** when done
3. **Use descriptive selectors**: role, text, test-id over CSS
4. **Add appropriate waits**: `wait_for_selector()`, `wait_for_load_state()`
5. **Capture screenshots on failure** for debugging
6. **Keep tests independent** - each test should set up its own state
---
**This skill encodes**: Playwright best practices | Selector strategies | Wait patterns | Anti-pattern prevention | E2E testing workflowsRelated Skills
vitest-testing-patterns
Write tests using Vitest and React Testing Library. Use when creating unit tests, component tests, integration tests, or mocking dependencies. Activates for test file creation, mock patterns, coverage, and testing best practices.
skill-coach
Guides creation of high-quality Agent Skills with domain expertise, anti-pattern detection, and progressive disclosure best practices. Use when creating skills, reviewing existing skills, or when users mention improving skill quality, encoding expertise, or avoiding common AI tooling mistakes. Activate on keywords: create skill, review skill, skill quality, skill best practices, skill anti-patterns. NOT for general coding advice or non-skill Claude Code features.
3d-cv-labeling-2026
Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).
wisdom-accountability-coach
Longitudinal memory tracking, philosophy teaching, and personal accountability with compassion. Expert in pattern recognition, Stoicism/Buddhism, and growth guidance. Activate on 'accountability', 'philosophy', 'Stoicism', 'Buddhism', 'personal growth', 'commitment tracking', 'wisdom teaching'. NOT for therapy or mental health treatment (refer to professionals), crisis intervention, or replacing professional coaching credentials.
windows-95-web-designer
Modern web applications with authentic Windows 95 aesthetic. Gradient title bars, Start menu paradigm, taskbar patterns, 3D beveled chrome. Extrapolates Win95 to AI chatbots, mobile UIs, responsive layouts. Activate on 'windows 95', 'win95', 'start menu', 'taskbar', 'retro desktop', '95 aesthetic', 'clippy'. NOT for Windows 3.1 (use windows-3-1-web-designer), vaporwave/synthwave, macOS, flat design.
windows-3-1-web-designer
Modern web applications with authentic Windows 3.1 aesthetic. Solid navy title bars, Program Manager navigation, beveled borders, single window controls. Extrapolates Win31 to AI chatbots (Cue Card paradigm), mobile UIs (pocket computing). Activate on 'windows 3.1', 'win31', 'program manager', 'retro desktop', '90s aesthetic', 'beveled'. NOT for Windows 95 (use windows-95-web-designer - has gradients, Start menu), vaporwave/synthwave, macOS, flat design.
win31-pixel-art-designer
Expert in Windows 3.1 era pixel art and graphics. Creates icons, banners, splash screens, and UI assets with authentic 16/256-color palettes, dithering patterns, and Program Manager styling. Activate on 'win31 icons', 'pixel art 90s', 'retro icons', '16-color', 'dithering', 'program manager icons', 'VGA palette'. NOT for modern flat icons, vaporwave art, or high-res illustrations.
win31-audio-design
Expert in Windows 3.1 era sound vocabulary for modern web/mobile apps. Creates satisfying retro UI sounds using CC-licensed 8-bit audio, Web Audio API, and haptic coordination. Activate on 'win31 sounds', 'retro audio', '90s sound effects', 'chimes', 'tada', 'ding', 'satisfying UI sounds'. NOT for modern flat UI sounds, voice synthesis, or music composition.
wedding-immortalist
Transform thousands of wedding photos and hours of footage into an immersive 3D Gaussian Splatting experience with theatre mode replay, face-clustered guest roster, and AI-curated best photos per person. Expert in 3DGS pipelines, face clustering, aesthetic scoring, and adaptive design matching the couple's wedding theme (disco, rustic, modern, LGBTQ+ celebrations). Activate on "wedding photos", "wedding video", "3D wedding", "Gaussian Splatting wedding", "wedding memory", "wedding immortalize", "face clustering wedding", "best wedding photos". NOT for general photo editing (use native-app-designer), non-wedding 3DGS (use drone-inspection-specialist), or event planning (not a wedding planner).
websocket-streaming
Implements real-time bidirectional communication between DAG execution engines and visualization dashboards via WebSocket. Covers connection management, typed event protocols, reconnection with backoff, and React hook integration. Activate on "WebSocket", "real-time updates", "live streaming", "execution events", "state streaming", "push notifications". NOT for HTTP REST APIs, server-sent events (SSE), or general networking.
web-weather-creator
Master of stylized atmospheric effects using SVG filters and CSS animations. Creates clouds, waves, lightning, rain, fog, aurora borealis, god rays, lens flares, twilight skies, and ocean spray—all with a premium aesthetic that's stylized but never cheap-looking.
web-wave-designer
Creates realistic ocean and water wave effects for web using SVG filters (feTurbulence, feDisplacementMap), CSS animations, and layering techniques. Use for ocean backgrounds, underwater distortion, beach scenes, ripple effects, liquid glass, and water-themed UI. Activate on "ocean wave", "water effect", "SVG water", "ripple animation", "underwater distortion", "liquid glass", "wave animation", "feTurbulence water", "beach waves", "sea foam". NOT for 3D ocean simulation (use WebGL/Three.js), video water effects (use video editing), physics-based fluid simulation (use canvas/WebGL), or simple gradient backgrounds without wave motion.