browser-test

Automates browser UI tests for web applications using Chrome MCP tools and Codex.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mattphanm/Codex-Agentic --skill browser-test-mattphanm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/browser-test
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill browser-test-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated browser UI testing reduces manual QA time by validating user flows, visual states, and accessibility across web applications.

Core Features & Use Cases

  • UI interaction verification across components
  • Visual evidence capture and documentation
  • Regression checks for UI changes and stakeholder demos

Quick Start

Run the browser UI tests against your local server to validate core interactions.

Frequently Asked Questions about browser-test

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

FAQPage Schema
How do I automate browser UI tests for web applications?

Automate browser UI testing by using Chrome MCP tools to validate user interaction flows and visual states. This approach applies deterministic execution steps for element selection, interactions, and timing controls across local, staging, and production-like environments.

Can I capture visual test evidence during automated browser testing?

Yes, visual test evidence capture is supported during automated browser testing. The process runs via a structured test protocol that documents test results and collects evidence for UI component verification and regression checks.

Does Chrome MCP support regression testing for UI changes?

Chrome MCP supports regression testing for UI changes by applying a structured test protocol. It automates deterministic execution steps to verify UI components, user interaction flows, and visual states across staging and production-like setups.

What is the best way to verify user interaction flows across different environments?

The best way to verify user interaction flows is using automated browser testing with Chrome MCP. It applies deterministic test execution steps for element selection and timing controls across local, staging, and production-like environments.

Do I need a structured test protocol for automated browser testing?

A structured test protocol is required for automated browser testing to satisfy requirements for deterministic test execution steps. It ensures proper element selection, interactions, timing controls, and evidence collection during UI component verification.

Can I run automated browser tests against my local server?

Yes, you can run automated browser UI tests against your local server. The testing applies Chrome MCP tools to validate core interactions and verify UI components in local, staging, and production-like environments.