ce-test-browser

Automate end-to-end browser tests for pages affected by PRs or branches.

2|Updated May 8, 2026

Search Tags:#automation #testing #branch #PR #browser #agent-browser

Ready to run

npx skills add https://github.com/xotong/claude-marketplace --skill ce-test-browser-xotong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-test-browser
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-test-browser-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end browser verification to ensure pages affected by PRs or branches render correctly and interactions work as expected.

Core Features & Use Cases

Run end-to-end browser tests on pages affected by a PR or branch.
Map changed files to routes and validate key UI flows across the app.
Supports headed (visible) and headless modes for local and CI testing, with interactive snapshots.

Quick Start

Run ce-test-browser on the target PR or branch to begin automated browser tests.

Frequently Asked Questions about ce-test-browser

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

FAQPage Schema

How do I automate browser tests for pages affected by a PR?▼

To automate browser tests for PR-affected pages, you map changed files to routes and validate UI flows using the agent-browser CLI against a running dev server. This verifies rendering and interactions without manual checks.

What is automated end-to-end browser testing for changed routes?▼

Automated end-to-end browser testing for changed routes validates that pages affected by a branch render correctly and interactions work. It scopes tests to only modified files mapped to routes for efficient verification.

Do I need a running dev server to run automated browser tests on PR pages?▼

Yes, a running development server is required to run automated browser tests on PR pages. You also need the agent-browser CLI and a test plan that maps changed files to routes to execute the verification.

Can I run headless browser tests in CI pipelines for changed UI flows?▼

Yes, you can run headless browser tests in CI pipelines for changed UI flows. The testing tool supports both headless mode for CI pipelines and headed mode for local testing with interactive snapshots.

What is the best way to scope end-to-end tests to only changed pages?▼

The best way to scope end-to-end tests to changed pages is by using a test plan that maps changed files to routes. This ensures the browser tests cover only the affected UI flows rather than the entire application.

Why are my automated browser tests not covering the correct PR-affected routes?▼

Automated browser tests may not cover correct PR-affected routes if the test plan mapping changed files to routes is misconfigured. You must accurately map modified files to their corresponding routes before execution.