Home A - Z
Page Index

An Otter Wiki

Blame

383953 lisa 2026-08-26 13:41:28
sd: add C09 beta testing study pages (18 pages via the shared port script); hub link Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011wnT73o2z6piKdyVNGHhx2
1 
<!-- 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. -->
2
## Topics:
3
- Beta Testing
4
- Test Scenarios
5
- Data Collection from Beta Testers
6
- Reporting Results
7
- Modifications Based on Feedback
8
- Personas
9
10
11
> [!note]- Beta testing
12
> The phase of software testing where a sample of the intended audience tests the software in a real environment.
13
14
> [!note]- Test scenario
15
> A specific situation or workflow that a beta tester is asked to perform in order to evaluate the functionality, usability or reliability of the software.
16
17
> [!note]- Test plan
18
> A document that outlines the objectives, scope, schedule and approach for beta testing, including which features to test and what data to collect.
19
20
> [!note]- Personas
21
> Fictional characters created based on user research to represent the different user types that might use a service, application, product, site or brand.
22
23
> [!note]- Data collection
24
> The systematic gathering of feedback, observations and measurements from beta testers during and after testing sessions.
25
26
> [!note]- Observation (beta testing)
27
> Watching beta testers interact with the software to identify usability issues, confusion points or unexpected behaviours.
28
29
> [!note]- Survey
30
> A structured set of questions given to beta testers to collect quantitative and qualitative feedback about their experience with the software.
31
32
> [!note]- Bug report
33
> A documented record of an error or defect found during beta testing, typically including steps to reproduce, expected behaviour and actual behaviour.
34
35
> [!note]- Reporting results
36
> The process of compiling and presenting beta testing findings, including issues discovered, tester feedback and recommendations for improvement.
37
38
> [!note]- Modifications
39
> Changes made to the software based on feedback and issues identified during beta testing, aimed at improving functionality, usability or performance.
40
41
> [!note]- Functionality
42
> The range of operations that can be performed by a software system as defined by its requirements.
43
44
> [!note]- Usability
45
> The ease with which a user can interact with a software system to achieve their goals efficiently and satisfactorily.
46
47
> [!note]- Evaluation criteria
48
> Performance criteria made from the expectations and specification, used to judge whether the software meets its intended purpose.
49
50
> [!note]- Testing table
51
> A commonly used way to record evidence of functionality testing, documenting test cases, expected results and actual results.
52
53
> [!note]- Feedback
54
> Information provided by beta testers about their experience, including issues encountered, suggestions for improvement and overall satisfaction.
55
56
> [!note]- Priority (bug classification)
57
> A ranking assigned to an issue found during beta testing that indicates how urgently it needs to be addressed before release.