skills.rest
takemi-ohama
takemi-ohamaCOMMUNITY
Explore all skills by this author →
GitHub

browser-test

Automate browser-based UI testing with Playwright MCP or Chrome DevTools MCP.

Updated Jan 30, 2026
Search Tags:#automation#regression#playwright#ui-testing#web-automation#browser-testing#chromedevtools
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill browser-test-takemi-ohama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/browser-test
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill browser-test-takemi-ohama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web developers and QA teams spend significant time manually testing web applications; this Skill automates browser-based validation using Playwright MCP or Chrome DevTools MCP to ensure UI correctness and regression coverage.

Core Features & Use Cases

  • Automated browser interactions: navigate, click, fill forms, capture screenshots, and verify page state across test scenarios.
  • Cross-MCP automation: supports both Playwright MCP and Chrome DevTools MCP to run tests in compatible environments.
  • Regression and visual verification: run feature tests, collect logs, network events, and visual snapshots for quality assurance.
  • Use Case: Validate a checkout flow across multiple browsers and environments with automated UI validations and result reporting.

Quick Start

Run /ndf:browser-test to automatically validate the current branch's UI in a headless browser.

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 testing for web applications?▼

Automated browser UI testing validates web applications by simulating navigation, clicks, form filling, and screenshot capture across different browsers. Using Playwright MCP or Chrome DevTools MCP ensures UI correctness and provides regression coverage without manual effort.

Can I run automated regression tests across multiple browsers with Playwright?▼

Yes, you can run automated regression tests across multiple browsers using Playwright MCP. It executes feature tests, collects logs and network events, and captures visual snapshots to verify UI correctness throughout your development cycles.

Do I need Chrome DevTools MCP to validate a checkout flow with automated UI testing?▼

You can use either Chrome DevTools MCP or Playwright MCP to validate a checkout flow. Both integrations support automated browser interactions, page state verification, and result reporting across test scenarios without requiring manual testing.

What's the best way to capture screenshots and network events during web automation?▼

The best way to capture screenshots and network events during web automation is using Playwright MCP or Chrome DevTools MCP. These integrations collect visual snapshots and network logs during automated feature tests for quality assurance and regression verification.

How do I start headless browser testing for my current branch?▼

Start headless browser testing for your current branch by running the browser-test command. This automatically validates your UI changes in a headless browser environment using the configured Playwright MCP or Chrome DevTools MCP integrations.

Related Skills

Explore More Software Engineering Skills→
92Bilal2692Bilal26

browser-use

Automate browser tasks via a Playwright MCP server.

Community
Advanced
AutumnsGroveAutumnsGrove
26

webapp-testing

Automate end-to-end web testing across Chromium, Firefox, and WebKit with Playwright.

Community
Advanced
smarmen86smarmen86

ship

Automate branch merging, test execution, adversarial review, versioning, and pull request creation.

Community
Advanced
mymx2mymx2
4

webapp-testing

Automate local web app testing with Playwright and Python.

Community
Intermediate