browser-test

Name: browser-test
Availability: InStock
Author: LangWatch

Automate interactive browser feature validation via Playwright MCP on Chromium or Firefox.

3.5k|340|Updated Sep 9, 2023

Search Tags:#automation #qa #verification #playwright #web-testing #browser

Ready to run

npx skills add https://github.com/langwatch/langwatch --skill browser-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/langwatch/langwatch/tree/main/.claude/skills/browser-test
Command: npx skills add https://github.com/langwatch/langwatch --skill browser-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates interactive browser-based verification to ensure critical features work as expected by driving real browsers through Playwright MCP during development and QA.

Core Features & Use Cases

Interactive browser validation: launch a browser, navigate the app, and verify UI flows without writing test files.
Port-driven testing: run checks against a specific port (e.g., http://localhost:<port>) and optionally describe the feature to verify.
Reporting: summarize results and capture evidence during the run.

Quick Start

Launch the browser test on the target port and begin interactive validation of the specified feature.

Frequently Asked Questions about browser-test

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

FAQPage Schema

How do I run interactive browser testing without writing test files?▼

Interactive browser testing without test files is automated by driving real browsers through Playwright MCP, allowing you to launch the app, navigate pages, interact with UI, and verify outcomes directly without writing scripts.

Can I use Playwright MCP to validate features on a specific localhost port?▼

Yes, you can validate features on a specific localhost port by running port-driven checks against the target URL (e.g., http://localhost:<port>) and describing the feature you want to verify during the session.

What is automated browser-based feature validation using Playwright MCP?▼

Automated browser-based feature validation using Playwright MCP is a QA process that opens your web app in Chromium or Firefox, simulates user interactions, and reports outcomes to ensure critical features work as expected.

Does interactive web-testing with Playwright MCP support Chromium and Firefox?▼

Yes, interactive web-testing with Playwright MCP supports Chromium and Firefox, enforcing browser configuration to drive actions via the MCP workflow and report validation results across both browser engines.

What's the best way to verify UI flows during development without creating test scripts?▼

Verifying UI flows during development without test scripts is best handled by launching a real browser via Playwright MCP, navigating the app interactively, and capturing evidence and summarized results during the run.