webapp-testing

Web application testing toolkit using Playwright with Python. Use for verifying frontend functionality, debugging UI behavior, capturing browser screenshots, viewing browser logs, and automating web interactions.

5 stars

byvamseeachanta

View on GitHub Installation ↓

Best use case

webapp-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using webapp-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/webapp-testing/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/development/webapp-testing/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/webapp-testing/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How webapp-testing Compares

Feature / Agent	webapp-testing	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

AI Agents for Coding

Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.

SKILL.md Source

# Webapp Testing

## Overview

This toolkit enables testing local web applications using Playwright with Python for frontend verification, UI debugging, screenshot capture, and browser automation.

## Quick Start

```bash
# Install dependencies
pip install playwright pytest requests
playwright install chromium
```

```python
from playwright.sync_api import sync_playwright

with sync_playwright() as p:
    browser = p.chromium.launch(headless=True)
    page = browser.new_page()
    page.goto("http://localhost:3000")

    # Take screenshot
    page.screenshot(path="screenshot.png")

    # Get page content
    content = page.content()
    print(content)

    browser.close()
```

## When to Use

- Verifying frontend functionality after code changes
- Debugging UI behavior and layout issues
- Capturing screenshots for documentation
- Viewing browser console logs for errors
- Automating repetitive web interactions
- End-to-end testing of web applications
- Validating form submissions and user flows

## Related Skills

- [engineering-report-generator](../engineering-report-generator/SKILL.md) - Generate test reports
- [data-pipeline-processor](../data-pipeline-processor/SKILL.md) - Process test data
- [parallel-file-processor](../parallel-file-processor/SKILL.md) - Batch screenshot processing

---

## Version History

- **1.1.0** (2026-01-02): Upgraded to SKILL_TEMPLATE_v2 format with Quick Start, Usage Examples, Error Handling, Metrics, Execution Checklist
- **1.0.0** (2024-10-15): Initial release with Playwright patterns, server management, debugging tools

## Sub-Skills

- [Example 1: Screenshot Comparison Testing (+2)](example-1-screenshot-comparison-testing/SKILL.md)
- [Do (+1)](do/SKILL.md)

## Sub-Skills

- [Error Handling](error-handling/SKILL.md)
- [Execution Checklist](execution-checklist/SKILL.md)
- [Metrics](metrics/SKILL.md)
- [Dependencies](dependencies/SKILL.md)

## Sub-Skills

- [Static HTML (+2)](static-html/SKILL.md)
- [Wait for Dynamic Content (+5)](wait-for-dynamic-content/SKILL.md)
- [Start Server Before Testing (+1)](start-server-before-testing/SKILL.md)
- [Assertion Examples (+1)](assertion-examples/SKILL.md)
- [Slow Motion (+3)](slow-motion/SKILL.md)

Related Skills

testing-tdd-london

from vamseeachanta/workspace-hub

TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.

testing-production

from vamseeachanta/workspace-hub

Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.