phaser-movement-testing

name	phaser-movement-testing
description	Standardized patterns for testing Phaser game movement, including key state handling and collision verification. Use when testing player movement, collision detection, or when movement testing challenges occur. Phaser requires keydown/keyup pattern, not single press events.

Phaser Movement Testing

Overview

Standardize Phaser movement testing patterns. Phaser uses continuous key state checking, not discrete events.

Key Input Pattern

Phaser requires keydown/keyup pattern, not single press events

Pattern:

keydown ArrowRight
sleep 0.5
keyup ArrowRight

Why: Phaser checks key state continuously in update() loop, not on single events.

See references/key-input.md for detailed key input patterns.

Common Pitfalls: Browser Automation Limitations

CRITICAL: Browser automation keydown/keyup events don't work reliably with Phaser's input system.

Why Browser Automation Fails

Problem: Phaser's input system requires native browser events, but browser automation tools (agent-browser, Playwright, Puppeteer) generate synthetic events that Phaser doesn't recognize.

Observed Issue: Browser automation keydown/keyup commands don't trigger Phaser's key listeners, causing movement tests to fail.

Root Cause:

• Phaser checks key.isDown property in update() loop
• Browser automation generates synthetic events