webapp-testing

Test local web apps with Playwright and server lifecycle scripts.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill webapp-testing-clay-hhk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/webapp-testing
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill webapp-testing-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Local web applications are often hard to test reliably because they require coordinating one or more local servers, waiting for dynamic JavaScript to finish rendering, discovering stable selectors, and capturing browser state for debugging and verification.

Core Features & Use Cases

  • Server orchestration: Helper script scripts/with_server.py starts one or more local servers, waits for readiness on specified ports, runs a given command, and then cleans up processes.
  • Reconnaissance-then-action testing: Use Playwright-based Python scripts to wait for networkidle, inspect rendered DOM, discover selectors, and then perform deterministic interactions.
  • Debugging and artifacts: Capture full-page screenshots, save console logs, and record element discovery output to aid debugging.
  • Use Case: Run a frontend and backend together, wait for both to be ready, discover selectors from the rendered page, and execute automated UI checks while saving screenshots and console output for CI diagnostics.

Quick Start

Start the servers with the helper and run a Playwright automation script that navigates to the local app, waits for network idle, captures a screenshot, and collects console logs.

Frequently Asked Questions about webapp-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate local web app testing with Playwright and Python?

Console logs are collected during automated browser testing by executing Python Playwright scripts that listen for console events while navigating your local web app. This captures frontend errors and output, saving them as artifacts to aid debugging and CI diagnostics.

What is the best way to coordinate frontend and backend servers during automated UI testing?

The best way to coordinate local servers during UI testing is using a server orchestration helper script. It starts one or more local servers, waits for readiness on specified ports, runs a given testing command, and then cleans up the processes automatically.

How do I capture full-page screenshots during browser automation?

You capture full-page screenshots during browser automation by running a Playwright Python script that navigates to your local web app, waits for the page to reach a networkidle load state, and saves the rendered page output as an image artifact for debugging.

Does this testing approach work with dynamic JavaScript web apps?

Yes, this approach works with dynamic JavaScript web apps by waiting for the networkidle load state before inspecting the rendered DOM. This ensures dynamic content has finished rendering before performing deterministic interactions or capturing browser state.

Why do my automated UI checks fail to find stable selectors on a local web app?

Automated UI checks fail to find selectors when dynamic JavaScript has not finished rendering. You can fix this by using a reconnaissance-then-action testing approach that waits for networkidle before discovering stable selectors from the fully rendered DOM.