webapp-testing

Automate Playwright browser testing for local dynamic web applications with server lifecycle management.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Maykesantos98/Fiap-Totvs --skill webapp-testing-maykesantos98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/Maykesantos98/Fiap-Totvs/tree/main/.claude/skills/webapp-testing
Command: npx skills add https://github.com/Maykesantos98/Fiap-Totvs --skill webapp-testing-maykesantos98

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It helps you reliably test dynamic local web applications without manually clicking through UI flows, making it easier to verify behavior, debug issues, and capture evidence (screenshots and logs).

Core Features & Use Cases

  • Server-aware testing workflow: Starts one or more local servers (or detects that they are already running) so Playwright can interact with the correct URLs.
  • Deterministic automation patterns: Guides you to wait for networkidle before inspecting the DOM to avoid timing flakiness on dynamic apps.
  • UI validation and debugging: Supports reconnaissance-then-action using rendered DOM inspection, plus screenshot capture and console-log capture to diagnose problems.
  • Use case: Validate that a Next.js/Fastify/FastAPI UI renders expected elements after network activity, then capture screenshots and browser console logs when something fails.

Quick Start

Run the command python scripts/with_server.py --help to learn how to start your local server(s) and execute a Playwright automation script safely.

Frequently Asked Questions about webapp-testing

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

FAQPage Schema
How do I automate UI testing for local web apps with Playwright?

Automate UI testing for local web apps by guiding Playwright through reconnaissance, interaction, and verification. Use a helper script to start local servers and wait for network idle before DOM inspection to reliably test dynamic applications.

Why does my Playwright UI testing fail on dynamic local web apps?

Playwright UI testing on dynamic local web apps often fails due to timing flakiness. Waiting for networkidle before inspecting the rendered DOM reduces test flakiness and ensures expected UI elements have fully loaded.

Can I capture screenshots and console logs during browser automation testing?

Yes, capture screenshots and console logs during browser automation testing to diagnose problems and verify behavior. This helps you debug UI failures and collect visual evidence without manually clicking through application flows.

Do I need to manually start my local server before running Playwright tests?

No, you do not need to manually start your local server. The server-aware testing workflow can start one or more local servers automatically, or detect existing running servers, so Playwright can interact with the correct URLs safely.

What is the best way to test multi-server local web app setups?

The best way to test multi-server local web app setups is using a provided helper script for lifecycle management. It safely starts multiple servers, executes Playwright automation, and manages the complete testing workflow deterministically.