Module 4 - BUILD
Implementing a digital escape game
6. Technical testing and playtesting protocol
6.1 Technical checklist before testing
Navigation test (systematic)
- Click every visible button in order.
- Confirm every button goes to the correct page.
- Confirm there is always a way forward and no blockage.
Interaction test
- Trigger every interaction (reveal / unlock / type-in / drag-and-drop).
- Try wrong answers deliberately:
- Do you get adequate feedback?
- Can you try again with hints?
- Try correct answers: Does it unlock what it should?
Media test
- Do images or videos load?
- Does sound work (if used)?
- If media fails, does the game still make sense?
External tool test (if used)
- Open any external elements or embedded tools.
- Test them on a second device.
- Create a fallback plan if they fail (“open in new tab” button or alternative clue in hybrid format, such as physical documents).
6.2 Run a playtest session
- Give the link to 2-4 people who did not work on the game, with minimal instructions (as real players would receive).
- Ask them to “think aloud” (say what they are trying to do or what they’re confused about).
- Observe silently as much as possible and take notes of:
- Where they get stuck
- What they misunderstand
- Where they misclick
- Which instructions they ignore
Activity: Matching
What should you look for when playtesting? Match the key aspects to the criteria you should focus on.
6.3 Use a bug & confusion log (template)
Page/screen name:
What happened:
What should happen:
Fix idea:
Priority: High / Medium / Low
Prioritise fixes:
- High: Stops progress, breaks game, causes major frustration
- Medium: Confusion but still possible to continue
- Low: Cosmetic, small improvements
6.4 Final stability checks
- Retest after every fix (small changes can break other things). Check every interaction, button, link, media and feedback process.
- Confirm your sharing settings (correct privacy and access).
- Duplicate your project as a final backup version.