ce-test-browser

Automates end-to-end browser testing of PR-affected pages using agent-browser CLI.

10|Updated Dec 13, 2016

Search Tags:#automation #testing #qa #branch #pr #browser

Ready to run

npx skills add https://github.com/vitallium/dotfiles --skill ce-test-browser-vitallium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-test-browser
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-test-browser-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end browser testing for pages affected by PRs or branch changes, reducing manual QA time and increasing test coverage.

Core Features & Use Cases

Deterministic browser actions: Open pages, interact with elements, and capture rendered content using the agent-browser CLI.
Scope-aware testing: Detect modified files from PRs or branches and map them to testable routes to focus validation.
Configurable execution: Support headed or headless modes, port management, and human verification steps for sensitive flows.

Quick Start

Provide a PR number or branch name to start 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 testing for PR changes?▼

Automated browser testing for PR changes uses the agent-browser CLI to validate affected pages by providing a PR number or branch name. It maps modified files to testable routes, executing deterministic browser actions and capturing rendered content to reduce manual QA time.

What is scope-aware browser testing and how does it work?▼

Scope-aware browser testing detects modified files from PRs or branches and maps them to testable routes to focus validation. This ensures automated end-to-end tests only target pages affected by recent code changes, increasing test coverage efficiency.

Can I run automated browser tests in headed mode for human verification?▼

Yes, automated browser tests support configurable execution with both headed and headless modes. Headed mode enables human verification steps for sensitive flows, while port management and route coverage mapping ensure structured result reporting across PR-affected pages.

How do I manage ports and prerequisites for end-to-end browser testing?▼

End-to-end browser testing handles port management automatically as part of its execution configuration. It fulfills requirements for prerequisites and port handling, allowing the agent-browser CLI to open pages, interact with elements, and validate changes across branches or PRs.

What's the best way to validate route coverage mapping for branch changes?▼

The best way to validate route coverage mapping for branch changes is using scope-aware testing that detects modified files and maps them to testable routes. This focuses automated browser validation on affected pages and generates structured result reporting.

Does automated browser testing work with branch changes instead of PRs?▼

Yes, automated browser testing is applicable when validating changes across both PRs and branches. You provide a branch name instead of a PR number, and the agent-browser CLI derives the test scope and maps modified files to routes for validation.