C09 — Skills in Conducting Beta Testing
The Hamilton and Alexandra College · Year 12 · 2026
Beta testing puts your software in front of real potential users and turns what they do into evidence-backed recommendations. C9 runs as a cycle: plan it, rehearse it in the simulation, conduct it and keep the raw evidence, present that evidence, analyse it into findings, and recommend modifications you defend live.
How C9 runs
| Indicator | Checkpoint | Validation |
|---|---|---|
| C9-1 Beta Testing Plan | Draft plan (feedback loop) | Beta Testing Simulation 🔒📱⏰ |
| C9-2 Conducting Beta Testing | — | Raw data pack + Raw Data Presentation 🔒📱⏰ |
| C9-3 Beta Testing Results | Draft Results & Analysis — §2 (feedback loop) | via C9-4's viva |
| C9-4 Recommended Modifications | Portfolio — §3 + mockups + traceability map (feedback loop) | Beta Recommendations Viva voce 🔒📱⏰ |
Recordings (audio + video) and signed consent forms live on your school OneDrive; your GitHub repo keeps instruments, exports, the deviation note and the pack index. The full specifications are the two assessment packages in your S-C09 folder.
Foundations
- Essential Terms
- The Four-Step Beta Testing Journey
- Priority Matrix
- Timeline and Resource Considerations
- Beta Testing Case Study: Pocket Prep
Stage 1 — Plan (C9-1)
- Beta Testing Plan — Three Levels
- Beta Testing Plan Template
- Beta Testing Plan Example — Godot Tetris
- Test Scenario Template
- Test Scenario — FitTrack