skills.rest
wangrenzhu-ola
wangrenzhu-olaCOMMUNITY
Explore all skills by this author →
GitHub

test-browser

Run end-to-end browser tests on pages affected by PR or branch changes.

2|1|Updated Apr 17, 2026
Search Tags:#automation#testing#qa#branch#pr#browser#agent-browser
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill test-browser-wangrenzhu-ola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/test-browser
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill test-browser-wangrenzhu-ola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser validation is slow and noisy; it should focus on pages touched by a PR or branch to accelerate release cycles.

Core Features & Use Cases

  • Focused testing on PR/branch changes by mapping changed files to routes and executing end-to-end browser actions via agent-browser.
  • Environment-aware support for headed or headless modes, with automatic port discovery and snapshot capture for visual verification.
  • Use Case: validate critical flows across modified pages and generate visual evidence for reviewers.

Quick Start

Run browser tests on PR-affected pages using the agent-browser CLI.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run browser tests only on pages affected by a PR?▼

You can run focused browser tests on PR-affected pages by mapping changed files to specific routes and executing end-to-end actions via the agent-browser CLI. This targets validation only at modified frontend pages to accelerate release cycles and reduce noisy test execution.

What is the best way to automate end-to-end testing for modified routes?▼

Automating end-to-end testing for modified routes is best handled by mapping PR or branch changes to frontend routes and executing browser actions via the agent-browser CLI. This targeted approach avoids testing unchanged pages and generates visual snapshots for reviewer evidence.

Do I need a local development server to run browser tests on PR-affected pages?▼

Yes, you need a local development server and the agent-browser CLI installed to run browser tests on PR-affected pages. The environment-aware execution automatically discovers ports and supports both headed and headless modes to validate modified routes.

How does visual verification work for frontend QA during branch testing?▼

Visual verification for frontend QA works by capturing snapshots of pages affected by branch changes during browser test execution. The agent-browser CLI generates this visual evidence automatically, allowing reviewers to validate critical flows across modified pages.

Can I use headless mode for browser testing on modified frontend routes?▼

Yes, you can use headless mode for browser testing on modified frontend routes. The environment-aware execution supports both headed and headless browser modes, automatically discovering local development server ports to execute tests and capture visual snapshots.

Related Skills

Explore More Software Engineering Skills→
Ouro-labsOuro-labs
14

ce-test-browser

Automate browser testing of web pages changed in pull requests or branches using agent-browser CLI.

Official
Intermediate
ArieGoldkinArieGoldkin
10

evidence-verification

Collect and verify test, build, and code-quality evidence before task completion.

Community
Intermediate
kwam1nakwam1na

ce-test-browser

Automate end-to-end browser testing for PR or branch changes.

Community
Advanced
drhazemibclcdrhazemibclc

test-browser

Runs browser-based end-to-end tests on pages affected by a PR or branch using agent-browser CLI.

Community
Advanced