webapp-testing_skill

This skill helps you test local web apps with Playwright, automate UI, capture screenshots, and inspect browser logs for faster debugging.

Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill enoch-robinson/agent-skill-collection --skill webapp-testing

SKILL.md2.8 KB

Overview

This skill is a Web Application Testing toolkit that uses Playwright for front-end automation, UI debugging, screenshots, and browser log inspection. It targets local and dynamic web apps and helps validate UI behavior and end-to-end flows. The toolset includes common locator patterns, wait strategies, and server orchestration tips for reliable tests.

How this skill works

The skill drives a browser (Chromium) via Playwright to navigate pages, wait for network idle or specific selectors, interact with elements (click, fill, role/text-based selectors), and capture screenshots or page content. It supports starting a dev server when needed, probing the running app, identifying selectors, and executing scripted interactions. Built-in wait strategies and locator patterns reduce flakiness and reveal UI state for debugging.

When to use it

Testing local static HTML or single-page applications before deployment
Automating end-to-end checks for UI flows like login, forms, and navigation
Capturing screenshots for visual regression or debugging layout issues
Inspecting browser DOM, logs, and responses during development
Running automated checks in CI after starting the application server

Best practices

Always wait for networkidle on dynamic apps before interacting
Prefer descriptive selectors: text=, role=, and IDs over brittle CSS paths
Use wait_for_selector for element-driven synchronization instead of fixed sleeps
Run headless in automation (headless=True) and close the browser after tests
Encapsulate server startup/shutdown in scripts so tests run reliably in CI

Example use cases

Automate a login flow: navigate, fill username/password, click submit, assert result text
Smoke test a local dev server: start server, wait for networkidle, capture a full-page screenshot
Debug intermittent UI failures by taking element-level screenshots and saving page.content() at failure time
Validate form behavior: fill fields, submit, wait for selector with success message, extract response text
Run a CI job that starts the app, runs Playwright scripts, and fails on missing selectors or JS errors

FAQ

For dynamic apps, yes: start the server or use a wrapper that launches the server before the Playwright script runs.

How do I avoid flaky tests?

Use networkidle and wait_for_selector for synchronization, prefer descriptive selectors, and avoid hard-coded sleep timers.