game-qa

Automate visual regression, gameplay verification, and performance testing for browser games.

307|37|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/OpusGameLabs/game-creator --skill game-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-qa
Source: https://github.com/OpusGameLabs/game-creator/tree/main/skills/game-qa
Command: npx skills add https://github.com/OpusGameLabs/game-creator --skill game-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables automated QA for browser games by performing visual regression checks, validating gameplay flows, and evaluating performance.

Core Features & Use Cases

  • Visual regression checks across game scenes and menus to detect unintended UI changes.
  • Gameplay verification to ensure boot flow, scene transitions, input handling, and scoring behave as expected.
  • Performance monitoring to keep FPS within budgets and detect regressions over time.

Quick Start

Install Playwright and Axe-core, set up a basic test harness, and run automated tests against your game project.

Frequently Asked Questions about game-qa

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

FAQPage Schema
How do I automate visual regression testing for browser games?

Automated visual regression testing for browser games uses Playwright to capture and compare scene snapshots, detecting unintended UI changes across menus and gameplay. It requires a Vite dev server and a test harness exposing game state on window for deterministic checks.

Can I run end-to-end gameplay verification on Phaser and Three.js games?

End-to-end gameplay verification supports 2D and 3D browser games built with engines like Phaser and Three.js. It validates boot sequences, scene transitions, input handling, and scoring by interacting with the game through a Playwright test harness.

What's the best way to monitor FPS performance regressions in browser games?

Performance monitoring tracks FPS during automated Playwright test runs to keep frame rates within budgets and detect regressions over time. This applies to 2D and 3D browser games running on a local dev server.

Do I need to expose game state on the window object for Playwright testing?

Yes, deterministic end-to-end tests require a testing harness that exposes the game state on window, such as window.__GAME__. This allows Playwright and Axe-core to access internal state for validating gameplay flows and accessibility checks.

How do I add accessibility checks to my browser game test suite?

Accessibility checks integrate Axe-core with Playwright to scan browser game menus and UI for compliance issues. The test harness runs these checks alongside gameplay verification and visual regression during automated test execution.

What are the limitations of using Playwright for browser game testing?

Playwright browser game testing requires a Vite or similar dev server integration and cannot test native runtime environments. Tests depend on exposing game state via window.__GAME__, limiting use to games that support this testing harness architecture.