browser-testing

Automate browser testing workflows using Chrome DevTools MCP and Browser-Use MCP.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/natslash/options-strategy-builder --skill browser-testing-natslash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing
Source: https://github.com/natslash/options-strategy-builder/tree/main/.claude/skills/browser-testing
Command: npx skills add https://github.com/natslash/options-strategy-builder --skill browser-testing-natslash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to automate browser-based testing workflows by combining Chrome DevTools MCP for inspection and Browser-Use MCP for human-like UI interactions. It streamlines debugging, performance analysis, and end-to-end UI validation across web applications.

Core Features & Use Cases

  • Dual-tool workflow: Chrome DevTools MCP for network, console, and performance tracing; Browser-Use MCP for sequence-based UI actions.
  • End-to-end testing scenarios: login flows, form submission, navigation, and accessibility checks.
  • Guided workflows: step-by-step patterns with verification points, state checks, and post-action validation.

Quick Start

Open a target page using chrome-devtools, perform a user flow with browser-use, and verify results with devtools.

Frequently Asked Questions about browser-testing

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

FAQPage Schema
How do I automate end-to-end browser testing workflows across web applications?

Automate end-to-end browser testing by orchestrating Chrome DevTools MCP for inspection and Browser-Use MCP for UI interactions. This dual-tool approach streamlines debugging, performance analysis, and UI validation with step-by-step guided workflows and post-action verification.

Can I perform network and performance tracing during web testing?

Yes, network and performance tracing during web testing is handled using Chrome DevTools MCP. It inspects console logs, network requests, and performance metrics, while Browser-Use MCP executes the sequence-based UI actions needed to trigger them.

Does this browser testing approach support login flows and form submission validation?

Yes, login flows, form submission, navigation, and accessibility checks are supported as core end-to-end testing scenarios. It validates these workflows using sequence-based UI actions combined with verification points and state checks.

What is the best way to validate UI interactions during automated web testing?

Validating UI interactions during automated web testing is best done by combining Browser-Use MCP for human-like sequence actions with Chrome DevTools MCP for post-action validation. This ensures safe session management and accurate state checks.

How do I debug web applications using Chrome DevTools and UI automation?

Debug web applications by opening a target page with Chrome DevTools, performing the user flow with Browser-Use, and verifying the results with DevTools. This guided workflow pattern includes per-action validation to ensure accurate debugging.