Gameplay Testing
Testing & Verification · Test level completion, character interactions, collision detection.
Gameplay Testing
What it is
Gameplay testing is manually playing the game from start to finish, looking for issues that an automated test can’t catch — collision misalignment, control responsiveness, pacing, fairness. It’s the test that requires a human in the loop.
Why it matters
Automated tests verify code behavior; gameplay testing verifies the experience. Some bugs are only obvious when you feel them — a jump that feels floaty, a hit box that connects too easily, a transition that lags. Only playing catches these.
How GateGame implements it
After every meaningful change I played the Maze of Shadows level start-to-finish. I verified the octopus can traverse the entire winding spline path without clipping through walls, that each NPC’s dialogue triggers on the right proximity, that the Exit Warden’s transition fires after picking ‘Step Through’, and that ‘Not yet’ cleanly closes the dialogue.
Code Example
// Gameplay test checklist (run after every change):
// ☑ player walks full maze path without clipping
// ☑ Shadow NPC dialogue triggers on collision
// ☑ Lantern NPC dialogue triggers on collision
// ☑ Exit Warden offers Step Through / Not yet
// ☑ Step Through fires fade + level transition
// ☑ Not yet closes dialogue cleanly
Key Takeaway
A short checklist run after every change catches the regressions that automated tests miss. It also forces you to play your own game, which is its own kind of feedback.