e2e-agent-browser

Automate browser end-to-end tests with accessibility snapshots and CI integration.

125|35|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/jh941213/my-claude-code-asset --skill e2e-agent-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-agent-browser
Source: https://github.com/jh941213/my-claude-code-asset/tree/main/skills/e2e-agent-browser
Command: npx skills add https://github.com/jh941213/my-claude-code-asset --skill e2e-agent-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated end-to-end browser testing using the agent-browser CLI, reducing manual testing time and increasing reliability through accessible snapshot checks and a robust reference system.

Core Features & Use Cases

  • Headless E2E Testing: Drive browser actions, assertions, and UI interactions with a single CLI.
  • Accessibility Snapshots & Ref System: Capture semantic snapshots and reusable element references for stable tests.
  • CI/CD & Reproducibility: Integrate tests into pipelines to validate UI flows across environments.

Quick Start

Install agent-browser globally, configure a base URL, and run the E2E runner to execute tests. Example: node templates/runner.js --url https://example.com --headed

Frequently Asked Questions about e2e-agent-browser

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

FAQPage Schema
How do I automate E2E browser testing for interactive UI checks in a CI pipeline?

Automate E2E browser testing by driving browser actions, assertions, and UI interactions using a single CLI, enabling headless execution and CI integration to validate UI flows across environments.

What are accessibility snapshots and how do they work for front-end testing?

Accessibility snapshots capture semantic snapshots of web pages for stable test verification. They enable snapshot-based verification by capturing the accessibility tree rather than pixel comparisons for reliable UI checks.

How do I use a ref system to interact with elements during headless E2E testing?

A ref system provides reusable element references for stable tests. It enables ref-based element interaction by assigning references to elements captured in accessibility snapshots, ensuring reliable targeting during headless execution.

Can I run E2E browser tests in headed mode for local debugging before CI integration?

Yes, you can run E2E browser tests in headed mode for local debugging. The runner supports a headed flag to execute tests with a visible browser UI before integrating them into headless CI pipelines.

Does agent-browser require any external dependencies to execute web app testing workflows?

No external dependencies are required. You can install agent-browser globally, configure a base URL, and run the E2E runner to execute tests without additional package installations.

What is the best way to validate UI flows across multiple environments with browser automation?

The best way is integrating tests into CI/CD pipelines to validate UI flows across environments. This approach ensures reproducibility by executing headless browser automation with consistent accessibility snapshots and ref-based interactions.