browser-testing

Drive Playwright to navigate pages, interact via accessibility references, and capture snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates browser-based UI testing by driving Playwright to navigate pages, interact with elements via accessibility references, and produce deterministic snapshots for verification.

Core Features & Use Cases

  • Deterministic UI testing using an accessibility tree instead of pixel-based input.
  • Navigation, clicking, typing, and form interactions, with automatic snapshot and console/network capture for debugging.
  • Use Case: Validate that a UI component renders correctly after a code change on a local server, then capture an accessibility snapshot and a screenshot for CI reports.

Quick Start

Use the browser_navigate tool to open a local page, then use browser_snapshot to capture the current accessibility tree, and follow up with browser_click using a known element ref to interact with the page.

Frequently Asked Questions about browser-testing

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

FAQPage Schema
How do I automate deterministic browser testing with Playwright?

Deterministic browser testing with Playwright is automated by driving navigation, interactions, and accessibility snapshots. The skill exposes tools like browser_navigate and browser_click to interact with pages and collect structured data rather than relying on pixel comparisons.

What is an accessibility snapshot for UI verification?

An accessibility snapshot for UI verification captures the current accessibility tree of a page. This provides deterministic structured data for validating that UI components render correctly after code changes, replacing fragile pixel-based comparisons.

Can I use this skill for regression testing on a local development server?

Yes, you can use this skill for regression testing on a local development server. It automates navigation, form interactions, and element clicking, while automatically capturing console and network data for debugging workflows.

How do I interact with web elements using Playwright accessibility references?

To interact with web elements, use the browser_snapshot tool to capture the page's accessibility tree, then use the browser_click tool with a known element ref. This method drives deterministic interactions without relying on visual coordinates.

Do I need Playwright installed to run automated UI tests?

Yes, you need Playwright installed at runtime to run automated UI tests. The skill requires Playwright to drive the browser, execute navigation, perform interactions, and collect accessibility snapshots for verification workflows.

Why use an accessibility tree instead of pixel comparisons for web testing?

Using an accessibility tree instead of pixel comparisons for web testing ensures deterministic results. It produces structured data that remains stable across minor visual changes, making CI verification and regression testing more reliable.