test-live

Run interactive Playwright MCP browser tests against a live web application.

1|1|Updated Feb 1, 2026

Search Tags:#browser automation #playwright #exploratory testing #live testing #authenticated testing #web app QA #UI issue reporting

Ready to run

npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill test-live

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-live
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/test-live
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill test-live

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly verify that a running web application behaves correctly by performing interactive browser-based testing instead of relying on manual clicks or outdated test cases.

Core Features & Use Cases

Interactive Playwright MCP testing: Drives a real browser session against your live URL to explore pages and interactions.
Optional authenticated flows: Supports login testing using provided username/email and password for scenarios that require auth.
Guided or exploratory scenarios: Runs either exploratory coverage (pages, forms, interactive elements, and console errors) or targeted instructions you specify for critical user journeys.
Structured reporting: Returns a summary of pages/forms tested, detected issues with severity, actionable recommendations, and any screenshots taken.

Quick Start

Run /workflow:test-live with your running site URL to trigger an exploratory browser test and receive a structured results summary.

Frequently Asked Questions about test-live

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

FAQPage Schema

How do I run exploratory browser testing against a live web app?▼

Interactive browser testing executes Playwright MCP automation against your running web application URL to perform exploratory UI checks and validate targeted user scenarios.

Can I test authenticated web app flows that require a login?▼

Authenticated testing supports login scenarios by utilizing optional username and password credentials to validate protected interactive flows within your web application.

How do I validate HTTP URLs before starting Playwright MCP automation?▼

URL validation requires a running http or https web address, and the process includes Playwright MCP availability checks with optional .claude/.mcp.json configuration guidance.

What reporting details are provided after testing interactive web pages?▼

Structured reporting returns a summary of tested pages and forms, detected UI issues with severity levels, actionable recommendations, and any screenshots taken during testing.

Does browser automation work for targeted user journey validation?▼

Playwright browser automation runs either exploratory coverage of pages and interactive elements or targeted instructions you specify for validating critical user journeys.