<!-- Generated from applied-computing-au vic/unit3-4/sat/C09-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. --> # 9-3 Basic Beta Testing Report Guide **C9-3 Assessment Preparation** - Skills in conducting beta testing: Documents the results of the beta tests --- ## 📋 How to Use This Guide **Follow each section below. Use your testing data to fill in the blanks. If you don't have something, leave it out or write 'not found.'** --- ## The 5-Category Results Framework ### Use Only the Categories Relevant to Your Testing **Choose the categories that match what you actually tested:** 1. **🪲 Bug Reports** - Technical issues and errors 2. **💡 Feature Requests** - User suggestions for improvements 3. **🔍 Usability Feedback** - User experience insights 4. **⚡ Performance Issues** - Speed, efficiency, and reliability 5. **💬 User Satisfaction** - Overall experience and ratings **You don't need all 5 categories - only include sections where you have actual data from your testing.** --- ## Basic Report Template ### **Beta Test Results for: [Your Software Name]** **Testing Details:** - **Testing Period:** [Start Date] to [End Date] - **Number of Testers:** [X] users - **Testing Methods:** [Survey, Observation, Interview] - **Main Testing Goal:** [What you wanted to find out] --- ### **🪲 Bug Reports** **Total Bugs Found:** [Number] **Most Important Problems:** **Problem 1:** [What went wrong?] - How many testers had this problem: ___ out of ___ testers - What they said: "[Quote from user]" - Why it matters: [How this affected their experience] **Problem 2:** [What went wrong?] - How many testers had this problem: ___ out of ___ testers - What they said: "[Quote from user]" - Why it matters: [How this affected their experience] **Other Problems:** - [List any other bugs you found] --- ### **💡 Feature Requests** **What Users Want Added:** **Request 1:** [What they want] - How many asked for this: ___ testers - Why they want it: "[What users said]" **Request 2:** [What they want] - How many asked for this: ___ testers - Why they want it: "[What users said]" **Request 3:** [What they want] - How many asked for this: ___ testers - Why they want it: "[What users said]" --- ### **🔍 Usability Results** **How Well Users Could Use Your Software:** **Task Success:** - Could complete main task: ___ out of ___ testers - Could find important features: ___ out of ___ testers - Overall ease of use rating: ___/10 average **What Users Struggled With:** - **Struggle 1:** [What was hard] - mentioned by ___ testers - **Struggle 2:** [What was hard] - mentioned by ___ testers **What Users Found Easy:** - **Easy thing 1:** [What worked well] - praised by ___ testers - **Easy thing 2:** [What worked well] - praised by ___ testers --- ### **⚡ Performance Results** **Speed and Reliability:** - How long to load: ___ seconds - App crashed: ___ times during testing - App froze: ___ times during testing **What Users Said About Speed:** - "[Quote about how fast/slow it felt]" - Rating for speed: ___/10 average --- ### **💬 User Satisfaction Summary** **Overall Ratings:** - Average satisfaction score: ___/10 - Would recommend to others: - 🟩 Yes – ___ testers - 🟥 No – ___ testers - Would keep using it: - 🟩 Yes – ___ testers - 🟥 No – ___ testers **What Users Said:** **Best Things About Your Software:** - "[Positive quote 1]" - "[Positive quote 2]" **Main Ideas to Make It Better:** - "[Improvement suggestion 1]" - "[Improvement suggestion 2]" --- ### **Summary of Key Findings** **Main Strengths:** 1. [Top thing that worked well + how many users agreed] 2. [Second thing that worked well + how many users agreed] **Main Issues to Fix:** 1. [Most important problem + how it affected users] 2. [Second important problem + how it affected users] **Overall Assessment:** [Write 1-2 sentences: Is your software ready to use, or what needs to be fixed first?] --- ## 🧾 Evidence Reminder **Always include:** - How many testers? - What did they say? - What does it mean? --- ## Success Checklist ### **Before You Submit:** ✅ I included the categories that match my testing ✅ I wrote numbers for how many testers said things ✅ I used real quotes from my testers ✅ I said what needs fixing or improving ✅ I checked my spelling and grammar --- ## Good vs. Poor Examples ### ✅ **Good Example:** > **Bug:** Login button doesn't work on phones - Affected 6 out of 8 testers > _What they said:_ "I tapped the login button but nothing happened" > _Why it matters:_ Users couldn't get into the app to use it ### ❌ **Poor Example:** > **Bug:** Login was broken > _What they said:_ "It didn't work" > _Why it matters:_ Users were frustrated ---