TEST SCRIPT

Controller Navigation Test Script

Run a short playtest to find focus traps, unclear prompts, and inconsistent Back behavior in game menus.

Why it matters

Many players use a controller for console and PC games, and a menu that works with a mouse can still trap someone with a gamepad. Focus can disappear, jump in an unexpected direction, or get stuck inside a pop-up. These issues rarely show up in static mockups, so a short scripted test is the fastest way to catch them before they become bug reports or negative reviews.

Set up

Connect the intended controller, start from a known save or prototype state, and log the build, platform, input device, and test date. Tell the player: “Use the controller as you normally would. I’ll give you a goal, and I’m testing the interface.”

Read these tasks aloud

From the pause menu, find and turn subtitles on. Open a settings panel, make a change, then leave without keeping it. Open a confirmation dialog, cancel it, and continue from where you were. If the game supports another device, repeat a task after switching inputs. Give goals without naming the buttons to press.

Log and retest

Record task, initial focus, expected path, actual inputs, outcome (independent, assisted, blocked), and evidence. Check if focus is always visible, movement follows a predictable order, Back restores focus, prompts match the active input, and nothing traps the player. Fix any blocker first and rerun the same start state.

Common mistakes to avoid

Naming the buttons in your instructions, which tests reading rather than the interface. Helping the player as soon as they hesitate. Testing only from the main menu instead of from realistic in-game states. Forgetting to switch input devices mid-session. Fixing several issues at once and then retesting from a different starting point, which makes it hard to know which change worked.

Use it in your portfolio

Record a short clip of a blocked or assisted task, then the same task after your fix. Add a one-line caption for each clip that explains the focus rule you changed. That before-and-after pairing is clear evidence of usability testing.

Keep going

Pair this with the Menu Architecture Map and the Accessibility Checklist, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.

Copyright 2026