Beta testing is a type of external user acceptance testing performed by potential or existing customers in a real-world environment. It typically occurs after internal validation and acceptance tests have been passed. The purpose is to validate the product in realistic contexts, identify usability issues, uncover defects that may have been missed in lab settings, and gather feedback for improvements.
Option C is correct because it best describes the intent and value of beta testing — to observe how the product performs in real-life configurations, which may include varying hardware, usage patterns, or business workflows.
Option A is incorrect — while some people use the terms loosely, beta testing is not a strict synonym for acceptance testing. Acceptance testing usually refers to more formal, criteria-driven testing (e.g., alpha or internal acceptance testing), while beta testing emphasizes broad, usage-based validation.
Option B is misleading — beta testers may follow scenarios, but beta testing is not typically based on predefined acceptance criteria alone. It emphasizes exploration in realistic use cases.
Option D is false — beta testing is not primarily about measuring test coverage. It is qualitative and feedback-driven rather than systematically structured.
Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 3.2):
“Beta testing is performed by users in their own environment and supports validation of the system in realistic operational conditions.”