# Ce Test Browser

Run browser tests for pages affected by the current branch or PR.

- Repository: https://github.com/EveryInc/compound-engineering-plugin (25818 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-browser -g -a claude-code -y`
Codex: `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-browser -g -a codex -y`
Cursor: `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-browser -g -a cursor -y`
Gemini CLI: `npx skills add EveryInc/compound-engineering-plugin --skill ce-test-browser -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EveryInc/compound-engineering-plugin`

## Description

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Browser Test Skill

Run end-to-end browser tests on pages affected by a PR or branch using the best approved browser driver available in the active harness.

**Done:** the run ends by reporting what it found, either the summary, with every affected route marked Pass, Fail, or Skip and each Skip carrying its reason, or, when a preflight blocker stops testing before any route can be exercised, the blocker and what would clear it. Reaching neither, or dropping a route from the summary because nobody could reach it, is the failure this done condition exists to prevent.

## Modes

- **Manual (default):** the user controls the dev server. When the fallback driver is `agent-browser`, ask whether to run headed or headless.
- **Pipeline (`mode:pipeline`):** invoked by LFG or another automated runner. The run is unattended, never block on a question. Read `references/pipeline-orchestration.md` from this skill's directory and follow it; it overrides port selection (step 4, Determine the dev server port), dev-server startup (step 5, Verify the dev server is running), and visibility prompts (step 6, Set visibility), running the same port script with `--free` inside the block that starts the server.

## Browser Driver Policy

Select the driver before the first browser action:

The rest: https://github.com/EveryInc/compound-engineering-plugin/blob/HEAD/skills/ce-test-browser/SKILL.md