browser-testing

Automate browser UI testing with snapshots, retries, and failure escalation.

3|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill browser-testing-bhaumikmaan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-testing
Source: https://github.com/bhaumikmaan/claude-code-master-skills/tree/main/skills/browser-testing
Command: npx skills add https://github.com/bhaumikmaan/claude-code-master-skills --skill browser-testing-bhaumikmaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, repeatable approach to automating browser interactions and verifying web UI behavior so tests are deterministic, token-efficient, and resilient to flaky DOM changes.

Core Features & Use Cases

  • Tab & Session Management: Open and track tabs within the user's existing browser session and avoid reusing stale tab IDs.
  • Snapshot-First Interactions: Capture page structure and ephemeral element references before every action to prevent stale-element errors.
  • Element Interaction & Forms: Robust element clicks, typed input, fill_form for multi-field submissions, and scroll-into-view handling for nested containers.
  • Observability: Targeted console log filtering, network request inspection, and selective screenshots (element-scoped or full-page) for evidence.
  • Failure Escalation & Verification: Short incremental waits, 2-3 retry limits, clear escalation when elements or navigation fail, and a PASS/FAIL verification workflow for frontend changes.
  • Use Case: Validate a new feature on a staging site by starting the dev server, navigating to the page, exercising form flows, checking console and network, and producing screenshots and a structured verdict.

Quick Start

Open the application's page in a new browser tab, snapshot the DOM, perform the intended interactions, capture console and network errors, and collect screenshots to report pass or fail.

Frequently Asked Questions about browser-testing

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

FAQPage Schema
How do I automate browser UI testing without running into stale element errors?▼

Automating browser UI testing reliably requires snapshotting the page structure to capture ephemeral element references before every interaction. This approach prevents stale-element errors by ensuring each action targets the most current DOM state.

What's the best way to verify frontend changes and report a pass or fail verdict?▼

Verifying frontend changes involves starting the dev server, navigating to the page, exercising form flows, and checking console and network logs. Capturing screenshots provides evidence to produce a structured pass or fail verdict.

How do I handle flaky DOM changes during automated web form testing?▼

Handling flaky DOM changes during web form testing requires robust element interactions, scroll-into-view handling for nested containers, and short incremental waits after navigation. Clear failure escalation occurs after 2-3 retries.

Can I capture network requests and console logs during automated browser testing?▼

Automated browser testing supports capturing network requests and console logs through targeted observability features. You can inspect network requests and filter console logs alongside taking element-scoped or full-page screenshots for evidence.

Does browser automation work with existing browser sessions for tab management?▼

Browser automation works with existing browser sessions by opening and tracking tabs within the current window. It avoids reusing stale tab IDs to maintain session integrity during multi-tab UI testing workflows.