ce-test-browser

Automate browser tests on web pages for code changes.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-test-browser-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-test-browser
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-test-browser-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates and validates browser tests for web pages, ensuring that code changes do not break the functionality of the application.

Core Features & Use Cases

  • Automated Browser Testing: Execute end-to-end tests on web pages automatically.
  • Manual Verification: Offers options for both headless and non-headless testing for visual inspection.
  • Integration with Local Development: Works seamlessly with local development servers and the agent-browser CLI.
  • Use Case: When deploying a new feature or fixing a bug, use this Skill to run tests on all affected pages to catch issues early.

Quick Start

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

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 tests for web pages affected by code changes?

Automate browser tests for web pages by running end-to-end test scripts against your local development server. This validates user interface and functionality automatically, ensuring code changes do not break application behavior.

Can I run end-to-end testing with a local development server and the agent-browser CLI?

Yes, you can run end-to-end testing seamlessly with a local development server using the agent-browser CLI. This integration allows you to execute browser tests directly on web pages affected by your code changes.

Does browser testing support headless and non-headless modes for visual inspection?

Browser testing supports both headless and non-headless modes for visual inspection. You can execute automated end-to-end tests non-headlessly to visually inspect web page user interfaces and verify functionality.

What is the best way to verify code changes do not break web application functionality?

The best way to verify code changes do not break web application functionality is to automate end-to-end browser tests on all affected web pages. This catches user interface and functional issues early before deployment.

When should I use automated browser testing for local development?

Use automated browser testing for local development when deploying a new feature or fixing a bug. Running tests on affected web pages catches functionality and user interface issues early in the development cycle.

Do I need the agent-browser CLI to execute browser tests on web pages?

Yes, you need the agent-browser CLI to execute browser tests on web pages. This Skill is intended for use with local development servers and the agent-browser CLI to validate user interface and functionality.