webapp-testing

Tests local web applications using Playwright scripts with automated server lifecycle management.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill webapp-testing-nt-boop-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/webapp-testing
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill webapp-testing-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve? Testing local web applications requires manually starting servers, waiting for them to be ready, and writing browser automation code, which is repetitive and error-prone when verifying frontend behavior or debugging UI issues. ## Core Features & Use Cases - Server Lifecycle Management: The with_server.py helper starts one or more servers, waits for port readiness, runs your automation, and cleans up processes automatically. - Playwright Browser Automation: Write native Python Playwright scripts to navigate pages, interact with elements, capture screenshots, and view console logs. - Reconnaissance-Then-Action Workflow: Inspect the rendered DOM after networkidle, identify selectors, then execute actions against dynamic webapps. - Use Case: Start a Vite dev server and a backend API together, then run a Playwright script that logs in, clicks through the UI, and captures a screenshot to verify a new feature works end to end. ## Quick Start Ask the AI to test your local web app by starting the dev server and running a Playwright script that navigates to the page and takes a screenshot.

Frequently Asked Questions about webapp-testing

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

FAQPage Schema
How do I test a local web application with Playwright?

Write a Python script using sync_playwright, launch Chromium in headless mode, navigate to the local server URL, and wait for networkidle before interacting with elements. Use the with_server.py helper to start the dev server automatically before your script runs.

How do I run Playwright tests that need multiple servers?

Pass multiple --server and --port pairs to with_server.py, such as one for a backend on port 3000 and a frontend on port 5173. The script starts each server, waits for its port to accept connections, then runs your automation command.

Why does my Playwright script fail to find elements on a dynamic page?

The script likely inspects the DOM before JavaScript finishes rendering. Call page.wait_for_load_state('networkidle') after navigation, then take a screenshot or read page.content() to discover the actual rendered selectors.

Can Playwright automate static HTML files without a server?

Yes, Playwright can open local HTML files directly using file:// URLs, so no server is needed. Read the HTML source first to identify selectors, then write the automation script against those known elements.

How do I capture browser console logs during Playwright automation?

Attach a listener to the page's console event before navigating, and record each message as it arrives. This captures JavaScript errors and log output during the automation session for debugging UI behavior.