game-testing

What problem does it solve?

Many browser-based Three.js games are difficult to validate consistently across development and CI environments, making regression detection, visual debugging, and input verification slow and manual. This Skill provides reproducible automation patterns to load the game, observe runtime state, capture visual evidence, and surface console errors so developers can iterate faster.

Core Features & Use Cases

• Load and render validation: Programmatically start a static server, open the game in a browser, and confirm canvas rendering and Three.js initialization.
• Input simulation & state inspection: Simulate keyboard and mouse events, read window-level game state, player position, camera data, and entity counts for deterministic checks.
• Visual debugging & CI integration: Capture screenshots, record errors and performance metrics, and run headless tests in CI for automated regression detection.

Quick Start

Start a local static server for your game's public folder and run the Playwright test to load the game, simulate input, and save screenshots for debugging.