skills.rest
FFCfelps1
FFCfelps1COMMUNITY
Explore all skills by this author →
GitHub

ce-test-browser

Automate end-to-end browser tests on PRs and branches using the agent-browser CLI.

1|Updated Jun 2, 2026
Search Tags:#PR automation#browser testing#end-to-end testing#web application testing#branch testing
One-click install
npx skills add https://github.com/FFCfelps1/SGPPF_Maua --skill ce-test-browser-ffcfelps1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/FFCfelps1/SGPPF_Maua/tree/main/.gemini/skills/ce-test-browser
Command: npx skills add https://github.com/FFCfelps1/SGPPF_Maua --skill ce-test-browser-ffcfelps1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the automation of end-to-end browser tests on pages affected by Pull Requests (PRs) or branch changes, ensuring the integrity of web applications without manual testing.

Core Features & Use Cases

  • Automated Browser Testing: Execute tests on web pages that have been modified due to code updates.
  • Integration with PRs and Branches: Run tests against specified PR numbers, branch names, or on the current branch.
  • Use Case: When a PR is submitted to a repository, the skill automatically runs browser tests on the affected pages to catch potential issues before they affect users.

Quick Start

Run browser tests on the current branch using the command: ce-test-browser current.

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 end-to-end browser testing for Pull Requests?▼

End-to-end browser testing for web applications is handled by invoking the agent-browser CLI to open pages, perform interactions, take screenshots, and scrape rendered content, ensuring changes in branches do not break functionality.

How do I run browser tests on the current branch?▼

To run browser tests on the current branch, execute the command 'ce-test-browser current', which triggers the agent-browser CLI to validate your local development server against recent code changes.

Do I need a local development server to run web application testing?▼

Yes, web application testing requires a local development server and the agent-browser CLI installation to properly execute end-to-end tests and verify branch changes.

Can I execute browser tests against a specific PR number or branch name?▼

Yes, you can execute browser tests against specified PR numbers or branch names to automatically verify modified web pages and catch potential issues before merging.

What is the best way to verify UI changes in feature branches without manual testing?▼

The best way to verify UI changes without manual testing is using PR automation to run end-to-end browser tests, taking screenshots and scraping rendered content to catch issues in feature branches.

Related Skills

Explore More Software Engineering Skills→
thisisryanswiftthisisryanswift
2

ce-test-browser

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

Community
Advanced
goofansugoofansu

shot-scraper

Capture automated web page screenshots in multiple formats and with flexible options.

Community
Advanced
softmgsoftmg

github-workflow-automation

Automate GitHub Actions workflow generation and CI/CD pipeline management.

Official
Advanced
CleanExpoCleanExpo
1

playwright-browser

Automate headless browser tasks and end-to-end tests with Playwright.

Community
Advanced