playtest

Automate browser-based visual QA testing for Mood with Playwright MCP.

1|Updated Mar 20, 2026

Search Tags:#qa #playwright #ui-testing #browser #visual-testing #playtest #game-debugging

Ready to run

npx skills add https://github.com/bsolidgold/mood --skill playtest-bsolidgold

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playtest
Source: https://github.com/bsolidgold/mood/tree/main/.claude/skills/playtest
Command: npx skills add https://github.com/bsolidgold/mood --skill playtest-bsolidgold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mood's browser-based playtesting requires manual verification of visuals and UI across start and gameplay states. This skill automates the process by launching the game, capturing screenshots, detecting console errors, and reporting state for quick QA feedback.

Core Features & Use Cases

Automated start-screen and gameplay screenshot capture using Playwright MCP.
Console error detection and basic game state reporting for quick issue triage.
Optional focus-area validation (sprites, minimap, combat, hud, start screen) for targeted checks.

Quick Start

Launch Mood in a local server and run Playwright MCP to capture the start screen and gameplay screenshots.

Frequently Asked Questions about playtest

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

FAQPage Schema

How do I automate browser-based visual QA testing for a game UI?▼

Automated visual QA testing launches the game in a browser via Playwright MCP, captures screenshots across start and gameplay states, detects console errors, and reports UI state for quick triage.

Can I target specific UI elements like sprites or the minimap during Playwright testing?▼

Yes, targeted visual checks support optional focus areas including sprites, minimap, combat, hud, and start screen, allowing you to validate specific rendering and gameplay states.

Do I need a local server running to capture gameplay screenshots with Playwright?▼

Yes, automated screenshot capture requires a local server running on port 7777, along with Playwright MCP tooling to launch the browser and capture the game states.

What's the best way to detect console errors during end-to-end browser testing?▼

Automated browser testing detects console errors during gameplay by launching the game via Playwright MCP, capturing state screenshots, and reporting any encountered errors for triage.

Does this visual testing approach work for both start screens and in-game sessions?▼

Yes, visual verification applies to end-to-end testing across both start screens and in-game sessions, capturing screenshots and reporting rendering and UI state for comprehensive coverage.