webapp-testing

Test web applications with Playwright browser automation, accessibility checks, and E2E audit strategies.

41|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill webapp-testing-devayoshaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/DevayoshaUS/Women-scholarship/tree/main/hackathon-main%20%281%29/hackathon-main/.agent/skills/webapp-testing
Command: npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill webapp-testing-devayoshaus

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Manually verifying every route, API endpoint, and UI component of a web application is slow and error-prone. This Skill provides a systematic deep-audit methodology plus an automated Playwright runner that loads pages, checks health signals, captures screenshots, and reports accessibility issues as structured JSON. ## Core Features & Use Cases - Automated Browser Testing: Run headless Chromium tests against any URL to verify page load status, titles, headings, element counts, and performance timings. - Accessibility Auditing: Check images for alt attributes, form labels, heading structure, and link text with a single command. - E2E Testing Guidance: Apply the testing pyramid, Page Object Model, CI integration, and anti-pattern guidance to structure Playwright test suites. - Use Case: Point the runner at a staging deployment to confirm all pages load, capture full-page screenshots for visual review, and flag accessibility gaps before release. ## Quick Start Ask the AI to run the Playwright runner script against your web app URL with the screenshot flag to get a JSON health report and a full-page screenshot.

Frequently Asked Questions about webapp-testing

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

FAQPage Schema
How do I run a Playwright browser test against a URL?▼

Run the playwright_runner.py script with a target URL to launch headless Chromium, load the page, and return a JSON report with status code, title, element counts, and performance timings. Add --screenshot to capture a full-page image.

How to check website accessibility with Playwright?▼

Run the script with the --a11y flag to audit a page for accessibility basics. It counts images missing alt attributes, form labels, heading structure across h1-h3, and links with text, returning results as JSON.

What should E2E tests cover in a web application?▼

Prioritize happy-path user flows first, then authentication flows, critical business actions, and error handling. Keep E2E tests limited to critical paths since they are expensive, and cover the rest with component and integration tests.

Why does the Playwright script fail to run?▼

The script requires the playwright Python package and a Chromium browser binary. Install both with pip install playwright followed by playwright install chromium, otherwise the script returns an error indicating Playwright is not installed.

When should I avoid using E2E tests?▼

Avoid E2E tests for individual UI components or implementation details, since they are slow and brittle. Use component and integration tests for those layers, and reserve E2E for critical user flows verified with stable data-testid selectors.