game-testing

Automate browser-based Three.js game testing with Playwright for loading, input, and rendering.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ElementTech/create-threejs-game --skill game-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-testing
Source: https://github.com/ElementTech/create-threejs-game/tree/main/template/.claude/skills/game-testing
Command: npx skills add https://github.com/ElementTech/create-threejs-game --skill game-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about game-testing

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

FAQPage Schema
How do I automate testing for a browser-based Three.js game?

Simulate keyboard and mouse input in Three.js games by dispatching Playwright browser automation events, then read runtime state like player position and camera data to verify input handling logic.

Can I capture screenshots of my Three.js game in a CI workflow?

Capture screenshots of Three.js games during CI workflows by running Playwright headless tests, which load the game via a static file server and save visual evidence for regression detection.

How do I collect console errors when running browser game automation?

Collect console errors during browser game automation by configuring Playwright to listen for page console events, surfacing JavaScript exceptions and Three.js initialization failures for debugging.

Does this game testing approach require a static file server?

Yes, this approach requires a static file server and Playwright to satisfy needs for headless or headed browser automation, DOM-evaluated game state inspection, and basic performance measurement.

What is the best way to detect rendering regressions in Three.js games?

Detect rendering regressions in Three.js games by programmatically validating canvas rendering and capturing screenshots in headless CI tests, comparing visual evidence across development iterations.