qa-browse

Test web applications with Playwright MCP and generate structured QA reports.

11|1|Updated Feb 7, 2026

Search Tags:#automation #qa #reporting #playwright #web-testing #bug-detection

Ready to run

npx skills add https://github.com/KSD-CO/IronCode --skill qa-browse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-browse
Source: https://github.com/KSD-CO/IronCode/tree/main/.ironcode/skill/qa-browse
Command: npx skills add https://github.com/KSD-CO/IronCode --skill qa-browse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers can systematically test web applications using Playwright MCP to produce structured QA reports and reproducible evidence, reducing manual testing time.

Core Features & Use Cases

Mode options: diff-aware, full, quick, and regression testing to cover development, release, and quick sanity checks.
Evidence & reporting: health scores, screenshots, and repro steps collected into a shareable report.
Direct MCP automation: uses browser_navigate, browser_snapshot, browser_click, and other MCP tools to drive tests without external scripts.

Quick Start

Run ironcode qa-browse against your target web app to start a diff-aware or full QA session and generate a structured report.

Frequently Asked Questions about qa-browse

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

FAQPage Schema

How do I automate web testing with Playwright to generate structured QA reports?▼

You can automate web testing with Playwright by using browser automation commands as MCP tools to drive tests, collect console errors, and generate structured QA reports with health scores and screenshots.

What testing modes are available for web application QA automation?▼

Available web QA testing modes include diff-aware, full, quick, and regression testing, designed to cover development feature branches, releases, and quick sanity checks.

How do I collect evidence like screenshots and repro steps during browser automation?▼

You collect evidence like screenshots and repro steps by running browser automation commands via Playwright MCP, which automatically captures and compiles this data into a shareable QA report.

Do I need a configured Playwright MCP server to run automated web tests?▼

Yes, you need a configured Playwright MCP server, because the testing process uses its browser automation commands as MCP tools to navigate, click, and snapshot web applications.

How does diff-aware QA testing work for feature branches?▼

Diff-aware QA testing works by systematically testing web applications to produce structured QA reports and reproducible evidence specifically targeted at changes within development feature branches.

Can I capture console errors while running automated browser tests?▼

Yes, the browser automation process uses MCP tools to drive tests and automatically collects console errors alongside health scores and screenshots into the final structured report.