Flip: Playtest

Every review runs Flip's automatic playtest (browser-playtest-v5) in a sandboxed headless Chromium with synthetic players and no real account. It boots the build, checks it draws something, times signalStart() (5 s target, 10 s limit) and transfer size, runs your flip-test.json, then drives Flip's own controller, which reaches your game as flip.on('input') events: menu, primary, right, left, primary. It checks the start, settle and game-over hooks, runs the test bridge twice, compares loaded media with asset-credits.json, and measures draw calls, triangles and texture sizes. It records the feed preview video in the same run.

flip-test.json:

{ "version": 1, "steps": [
  { "type": "click", "selector": "#play" },
  { "type": "gamepad", "button": "primary" },
  { "type": "gamepad", "stick": "left", "x": 1, "y": 0, "ms": 300 },
  { "type": "key", "key": "Space" },
  { "type": "assertText", "text": "You win" },
  { "type": "assertState", "path": "round.settled", "equals": true },
  { "type": "assertSignal", "signal": "settle" },
  { "type": "wait", "ms": 500 }
] }

Use 2–24 steps, with at least one input (click, key or gamepad) and one assertion (assertText, assertState or assertSignal). Waits and gamepad holds total at most 10 s. Gamepad buttons use the input stream's names: primary, jump, interact, secondary, run, menu, and up, down, left, right for the D-pad. Sticks use up as +1. assertState reads flip.test.snapshot() from your test bridge and polls for up to 3 s.