skills.rest
valegrajales
valegrajalesCOMMUNITY
Explore all skills by this author →
GitHub

test-browser

Automate end-to-end browser tests for UI and functional issues.

Updated Jun 4, 2026
Search Tags:#automation#UI testing#browser testing#end-to-end testing#PR testing
One-click install
npx skills add https://github.com/valegrajales/agentic-retrieval-example --skill test-browser-valegrajales
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/valegrajales/agentic-retrieval-example/tree/main/.github/skills/test-browser
Command: npx skills add https://github.com/valegrajales/agentic-retrieval-example --skill test-browser-valegrajales

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes scripts (resource) components.

What problem does it solve?

This Skill automates browser testing to identify issues in pages affected by code changes in a PR or branch, ensuring software quality and reducing manual testing efforts.

Core Features & Use Cases

  • Automated Testing: Execute end-to-end browser tests automatically for a given PR, branch, or 'current' state.
  • Prerequisites Check: Validates local development server, agent-browser CLI, and Git repository setup.
  • Flexible Scoping: Test based on PR numbers, branch names, or current changes, supporting various environments.
  • Headed or Headless Mode: Choose to watch tests running in a browser or run them in the background.
  • Human Verification: Provides options for human verification for flows requiring external interaction like OAuth, email, or payments.

Quick Start

Run browser tests on the current branch by typing /test-browser.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I automate end-to-end browser testing for a pull request?▼

Automate end-to-end browser testing for a pull request by running the testing Skill against specific PR numbers to identify UI and functional issues in affected pages, ensuring software quality and reducing manual testing efforts.

Do I need a local development server to run browser tests on my current branch?▼

Yes, running browser tests on your current branch requires a local development server, the agent-browser CLI installed, and a valid Git repository setup to validate prerequisites before executing automated browser interactions.

Can I run browser tests in headless mode for background processing?▼

Yes, you can run browser tests in headless mode for background processing or choose headed mode to watch tests running in a browser, providing flexibility for various end-to-end testing scenarios and local development environments.

How do I handle OAuth or payment flows during automated UI testing?▼

Handle OAuth, email, or payment flows during automated UI testing by utilizing the human verification options provided, allowing manual intervention for external interactions required by complex end-to-end testing scenarios.

What is the best way to scope browser testing to specific branch changes?▼

Scope browser testing to specific branch changes by targeting branch names, PR numbers, or the current state, allowing flexible scoping that supports various local development environments and identifies functional issues in affected web pages.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
9

dev-swarm-nodejs

Install and configure Node.js development environment with nvm and pnpm.

Official
Advanced
thisisryanswiftthisisryanswift
2

ce-test-browser

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

Community
Advanced
791994545791994545
4

dogfood

Automate browser-based end-to-end tests and generate reports with reproduction evidence.

Community
Advanced
jh941213jh941213
125

e2e-agent-browser

Automate browser end-to-end tests with accessibility snapshots and CI integration.

Community
Advanced