9-2 Beta Test Execution
Running Your Beta Test Session
You've planned your beta test (C9-1) and chosen your data collection methods. Now it's time to actually run the testing sessions with your users.
Before the Session
Prepare a consistent setup for every tester:
- Environment — Have the solution installed/accessible and ready to go. Remove any debug screens or developer tools visible to the user.
- Materials — Print or share your survey, observation sheet, and interview questions before the session starts.
- Briefing script — Write a short intro you'll read to every tester so they all receive the same information. Include what the software does, what you'd like them to try, and that honest feedback is welcome.
Tip: Do a quick dry run with a classmate first. This catches setup issues before your real testers arrive.
During the Session
| Do | Don't |
|---|---|
| Let the user explore naturally | Jump in and fix things for them |
| Take notes on what you observe | Only rely on what the user tells you |
| Use your planned test scenarios | Make up tasks on the spot |
| Record the session (with permission) | Forget to ask for consent first |
| Stay neutral — "Tell me more about that" | Lead with "Isn't this feature great?" |
Collecting Data As You Go
For each tester, you should be gathering evidence across your chosen methods simultaneously:
- Observation — Note task completion times, errors, hesitations and navigation paths as they happen.
- Survey — Hand this to the user immediately after they finish the test scenarios, while the experience is fresh.
- Interview — If using interviews, conduct these after the survey. Follow up on anything interesting you observed.
After Each Session
Before your next tester arrives:
- Label all data with the tester's identifier (e.g. "User A", "User B" — not real names in your submission).
- Save any screen recordings or photos.
- Jot down your own reflections while they're fresh — anything that surprised you or that you'd adjust for the next session.
Scaling Up: What the Criteria Expect
| Level | What's Expected |
|---|---|
| C9-2-1 | Conduct beta testing with one potential user |
| C9-2-3 | Conduct beta testing and list results using one data collection method |
| C9-2-5 | Conduct beta testing and collect results using two data collection methods |
| C9-2-7 | Conduct beta testing with multiple users and collect results using three or more data collection methods |
| C9-2-9 | Prepare the data collected for documenting the results |
To aim high, you need multiple users and three or more methods (e.g. survey + observation + interview). You also need to organise your raw data so it's ready for your results report in C9-3.
Quick Evidence Checklist
- Briefing script used consistently across testers
- Test scenarios followed as planned in C9-1
- Observation notes taken during each session
- Survey completed by each tester
- Interview responses recorded (if applicable)
- Screen recordings or photos saved (if applicable)
- All data labelled and organised by tester
- Raw data prepared and ready for C9-3 documentation
This activity connects directly to your C9-1 beta testing plan. The evidence you gather here feeds into your C9-3 results report and C9-4 recommendations.