Game Test Plan - Swapbound

Version: 0.1.0
Date: April 13, 2026
Status: Active prototype

1. Purpose

Define the verification approach for the current Swapbound game and level editor prototype.

start site/swapbound/game.html and confirm the page loads without console errors
verify player movement, jump, interact/down, and shared-control split are readable and functional
verify checkpoints respawn safely and lives/reset logic behaves correctly
verify block push/carry behavior remains stable on ground and moving platforms
verify switch targets control lifts/bridges/switches as designed
verify remap and keyswap events visibly update the control display and input behavior

start site/swapbound/editor.html and confirm the editor loads without console errors
create/select/move/resize objects on canvas
import and export level JSON
use Test level flow and confirm the runtime loads the editor-authored level
verify switch-target linking, platform path editing, and helper overlays remain usable

verify site/docs/swapbound.html lists changelog, specs, and verification/risk docs
verify site/docs/game-urs.html, game-fs.html, game-ds.html, game-risk-assessment.html, game-test-plan.html, game-iq.html, and game-oq.html render correctly
re-run npm run docs:render after markdown documentation updates

The current Swapbound prototype is acceptable when:

the game remains playable end-to-end through the intended rooms/levels
editor-authored content can be tested in the runtime without manual file surgery
remap/keyswap mechanics remain understandable
documentation and public HTML mirrors are present and in sync