skills.rest
jaydubya818
jaydubya818COMMUNITY
Explore all skills by this author →
GitHub

test-browser

Run end-to-end browser tests on routes affected by a PR or branch.

Updated Mar 26, 2026
Search Tags:#automation#qa#web-testing#pull-request#browser-testing#agent-browser
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill test-browser-jaydubya818
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/plugins/compound-engineering/skills/test-browser
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill test-browser-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser-based QA checks by running tests only on pages affected by a PR or branch, reducing manual regression effort.

Core Features & Use Cases

  • Selective scope: maps changed files to testable routes and generates a focused test set.
  • Port and server awareness: detects the correct dev server port from PR hints, env files, or package.json to ensure tests run against the right instance.
  • End-to-end testing with agent-browser: uses the agent-browser CLI to open pages, interact, snapshot, and verify UI behavior across affected routes.
  • Use Case: when validating a PR that changes the dashboard layout, tests automatically cover the modified routes and report regressions.

Quick Start

Run the skill on your current branch or PR to automatically identify changed routes and execute browser tests with agent-browser.

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 on only the pages affected by a pull request?▼

Browser tests for PR-affected pages run by mapping changed files to testable routes, determining the dev server port, and using agent-browser to execute and validate interactions. This selective scope reduces manual regression effort by focusing only on modified areas.

How do I find the correct dev server port for automated browser testing?▼

The dev server port for automated browser testing is detected from PR hints, environment files, or package.json configurations. This ensures tests execute against the correct local server instance without manual port specification.

Do I need agent-browser installed to run end-to-end web tests?▼

Yes, agent-browser must be installed to run end-to-end web tests. The skill uses the agent-browser CLI to open pages, interact with UI elements, snapshot visual states, and verify behavior across affected routes.

What is selective scope web testing and how does it map changed files to routes?▼

Selective scope web testing maps changed files in a branch or PR to testable routes, generating a focused test set. This approach ensures only pages touched by code changes undergo browser QA checks, reducing manual effort.

Can I use this browser testing skill without a running local server?▼

No, a running local server is required. The skill operates by opening pages and validating interactions on affected routes, which necessitates an active dev server instance and proper environment configuration.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-test-browser

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

Community
Advanced
AztecProtocolAztecProtocol
449

fix-pr

Analyze CI logs and apply targeted fixes to failing PRs.

Official
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
thisisryanswiftthisisryanswift
2

ce-test-browser

Automate end-to-end browser tests on PR-affected pages using agent-browser CLI.

Community
Advanced