3ed16c2aaf
Per your direction: tests must be able to debug UI/UX behaviors and
must be performant. Playwright's bundled Chromium falls to SwiftShader
on Linux which is fine for visual scenarios but tanks anything where
fps matters. New attach-mode lets us drive YOUR Chrome (hardware GPU)
without needing Playwright to spawn its own.
test/attach.py:
- One-shot health check that connects to localhost:9222 (Chrome
already running with --remote-debugging-port). Doesn't spawn,
doesn't close. Just confirms attach + reports the FPS HUD value.
- peek.py and run.py already attach via CDP, so they work as-is
once Chrome is started with the debug port.
test/README.md:
- New "Two modes" section up front: attach (your real Chrome,
hardware) vs launch (Playwright Chromium, software). Each has a
legitimate use; perf-sensitive work goes through attach.
- Workflow:
google-chrome --remote-debugging-port=9222 \\
--user-data-dir=/tmp/voxel-dev-chrome http://localhost:8080/
python3 attach.py # health check
python3 run.py scenarios/ui-menu-open-close.yaml
New UI scenarios that drive interactions via DOM events / wasm calls,
not pixel screenshots. Render-independent, fast on any backend:
ui-menu-open-close.yaml Click ≡ → assert menu-open class →
click resume → assert closed.
ui-hotbar.yaml pointerdown on slot 4 → assert .active
moved. Digit1 keypress → assert .active
back to slot 0.
ui-respawn.yaml teleport into void → wait → assert
is_alive()===false + body.dead class +
death screen visible. Click respawn-btn
→ assert hp===20, alive===true.
ui-settings-sliders.yaml Slider .value = N + dispatch 'input' →
assert displayed value updates → unwind
so the page isn't left frozen.
README updates list all scenarios. No code in the game changed —
this is pure test-harness additions.
31 lines
1.1 KiB
YAML
31 lines
1.1 KiB
YAML
name: ui-respawn
|
|
description: |
|
|
Die (teleport into the void), confirm death screen appears,
|
|
click respawn, confirm player is alive again. Verifies the
|
|
body.dead class drives #death visibility, that the respawn
|
|
button triggers the wasm respawn() call, and that the player
|
|
ends up alive in a sane position.
|
|
|
|
steps:
|
|
- wait_for: "window.voxel_game && document.getElementById('respawn-btn')"
|
|
|
|
# Confirm alive at start.
|
|
- assert: "window.voxel_game.is_alive() === true"
|
|
- assert: "!document.body.classList.contains('dead')"
|
|
|
|
# Teleport into the void to trigger void-death.
|
|
- eval: "window.voxel_game.teleport(0, -50, 0)"
|
|
- wait: 1500 # let physics tick fire & damage land
|
|
|
|
- assert: "window.voxel_game.is_alive() === false"
|
|
- assert: "document.body.classList.contains('dead')"
|
|
- screenshot: 01-dead.png
|
|
|
|
# Click respawn.
|
|
- eval: "document.getElementById('respawn-btn').click()"
|
|
- wait: 800
|
|
|
|
- assert: "window.voxel_game.is_alive() === true"
|
|
- assert: "window.voxel_game.get_hp() === 20"
|
|
- assert: "!document.body.classList.contains('dead')"
|
|
- screenshot: 02-respawned.png
|