[ GAME DEVELOPMENT ]
VR Playtesting Guide: Running Sessions That Teach You Something
A useful VR playtest makes the play space safe, gives testers one clear task, observes without interrupting, and records two things: where people feel uncomfortable and where they get confused. Run sessions one tester at a time, reset the space between them, and write up your notes while the session is still fresh. A small, consistent process will teach you more than a big, messy one.
How should you prepare the play space?
Start before the tester arrives. Clear the floor of cables, rugs, pets and anything that could be tripped over. Move breakables and sharp corners out of reach, and mark the boundary so the tester knows where the safe area ends. Keep water and a chair nearby, with a spot ready for the tester to sit if they need a break.
Assign a spotter, a person whose only job is to watch the tester's safety. The spotter should stay close enough to act but far enough away not to crowd the tester. Check the headset fit before the session starts, and have wipes and a clean cloth ready for the lenses and straps.
For a deeper checklist on the comfort side, read a VR playtest safety and comfort protocol.
How do you brief testers?
Explain what you want to learn, not what they should do. "We want to see whether the first ten minutes are clear" sets a goal without telling the tester where to go. Tell them they can stop or take a break at any time, and explain how to ask for one. Ask them to think out loud, but do not coach them when they get stuck.
If you record the session, get consent before the headset goes on. Be clear about what is recorded, where it will be stored and who will see it.
What should you watch for?
During the session, the observer should note behavior rather than interpret it. Some patterns are easy to spot:
| What you see | What it may mean | What to note |
|---|---|---|
| The tester pauses before a choice | Unclear options or too much text | The screen, the time and what they said |
| The tester turns away from a target | Comfort or spatial awareness issues | Where they were and what caused the turn |
| The tester reaches for something that is not there | The interface does not match their expectations | The gesture and the object they wanted |
| The tester asks for a break | Discomfort or fatigue | The time, the activity and their words |
Write down exact words when you can. A quote such as "I thought that door was locked" is far more useful than your summary of it.
How do you run the session? A one-page plan
- Before the headset goes on, confirm consent and explain the stop rules.
- Set the play height and boundary, and show the comfort options.
- Give one goal for the session, not a full tutorial.
- Observe silently and write notes without coaching.
- After each segment, ask two open questions, such as what they expected and what surprised them.
- Offer a break before the tester seems tired, and end early if anyone shows discomfort.
- Debrief: ask what they remember, what felt off and what they would change.
- Reset the equipment and log what happened.
This plan works for a small team with one headset and one observer. Keep it the same across sessions so your notes can be compared.
How do you collect what you learn?
Use a simple template for each session. Include the tester's headset and experience level, their own description of comfort, a list of confusion points with timestamps, exact quotes, bugs and action items. Add a short summary at the end, but keep the raw notes too. The raw notes are where patterns show up across sessions. For more on running feedback sessions, see collecting feedback from VR playtesters.
What should you do when a tester feels unwell?
Stop the session as soon as a tester shows signs of discomfort, even if they say they are fine. Help them take the headset off slowly, sit them down and check how they feel before you talk about the game. Do not ask them to try again that day. Write down what they were doing, how long they had been playing and what they described, because those details help you find the cause. If symptoms last or get worse, encourage them to seek medical advice. Your playtest is only useful if your testers are safe, and a short, polite stop is always the right call.
How do you clean equipment between sessions?
Reset the headset, straps and controllers between testers. Use the cleaning method your headset maker recommends, and never spray liquid directly onto the lenses. Replace face covers when they are worn or dirty, and check that the controllers are charged and working before the next tester arrives.
If you test across several headsets and runtimes, record which combination each session used. A QA testing matrix for VR headsets and runtimes helps you keep those combinations organized, so a bug report always comes with the setup that caused it.
Keep each session small, watch more than you talk, and write notes straight after each one. The goal is to find where people get confused or uncomfortable, not to prove the game works. Run the same plan with the next tester and compare the notes.
Frequently asked questions
How many testers do you need for a VR playtest?
Start with a few testers and add more when the same problems keep showing up. Repeated patterns across sessions matter more than the total number of people in the room.
How long should a VR playtest session last?
Keep sessions short enough that testers can stop before they feel unwell. Offer breaks, and end the session early if anyone shows signs of discomfort.
Should testers know what the game is about?
Tell them enough to set the task, but do not explain the mechanics you want to test. Their first reactions are the data you are looking for.
What should you do between VR playtests?
Clean the lenses, straps and controllers using the method your headset maker recommends, and reset the play space. Log what changed so the next session starts clean.