opsmachine/webapp-testing
skills/webapp-testing/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add opsmachine/om-agency webapp-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 6, 2026, 5:59 AM114.3s6 files scanned
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 Toolkit
This is a toolkit, not a workflow skill. It provides helper scripts and examples for E2E testing with Playwright.
Used by: TDD workflow skills (plan-tests, write-failing-test, implement-to-pass)
Primary reference: See shared/e2e-patterns.md for complete E2E testing patterns and guidance.
Contents
Helper Scripts:
scripts/with_server.py- Manages dev server lifecycle (supports multiple servers)
Examples:
examples/element_discovery.py- Discovering elements on a pageexamples/static_html_automation.py- Testing static HTML filesexamples/console_logging.py- Capturing browser console logs
Always run scripts with --help first. DO NOT read the source unless absolutely necessary. These scripts are designed as black-box utilities.
Quick Start
For complete E2E testing guidance: See shared/e2e-patterns.md
For project-specific patterns: See .claude/primitives/testing-conventions.md
When to Use This Toolkit
During TDD workflow:
- TDD skills reference these helpers automatically when writing E2E tests
- You typically won't invoke this skill directly
For ad-hoc browser automation:
- Debugging frontend issues
- Capturing screenshots of current state
- Testing browser behavior outside TDD workflow
Helper Scripts
with_server.py - Server Lifecycle Management
Manages dev server startup/shutdown for E2E tests. Run --help for full usage:
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()
Examples
Working code samples for common E2E scenarios:
examples/element_discovery.py- Discovering buttons, links, and inputs on a pageexamples/static_html_automation.py- Using file:// URLs for local HTMLexamples/console_logging.py- Capturing console logs during automation
Use these as starting points for E2E tests.
Integration with TDD Workflow
This toolkit is referenced by:
- plan-tests - When planning E2E tests
- write-failing-test - When writing E2E tests (uses
with_server.pyand patterns) - implement-to-pass - When implementing code to pass E2E tests
You don't need to invoke this skill directly during TDD. The workflow skills use it automatically.
For More Information
Complete E2E patterns: shared/e2e-patterns.md
Project-specific patterns: .claude/primitives/testing-conventions.md
Test planning guidance: shared/test-planning.md
Related Skills
opsmachine/write-failing-test
testing
VerifiedTrustedCommunity
Write failing tests for all planned acceptance criteria from the test plan. Use after /plan-tests, before implementation. Invoke with '/write-failing-test path/to/spec.md' or 'write failing test', 'red phase', 'start TDD'.
1SKILL.mdUpdated Jun 6, 2026
opsmachine/workflow-router
data-ai
VerifiedTrustedCommunity
Workflow manager that orchestrates the entire skill system. Runs automatically before any implementation work. Reads state from artifacts, determines the next skill, spawns sub-agents for execution, and manages human gates. Invoke with '/workflow-router' or it runs automatically per CLAUDE.md.
1SKILL.mdUpdated Jun 6, 2026
opsmachine/supabase-security
development
VerifiedTrustedCommunity
Supabase security best practices and patterns. Use when working with Supabase projects, creating tables, writing RLS policies, edge functions, or reviewing Supabase code. Invoke with '/supabase-security' or when asked about Supabase security.
1SKILL.mdUpdated Jun 6, 2026
opsmachine/spec-review
testing
VerifiedTrustedCommunity
Review a spec document for completeness before approval. Use after interview, before implementation, or when asked to 'review spec', 'check spec', or 'is this spec ready'. Read-only analysis that flags gaps.
1SKILL.mdUpdated Jun 6, 2026