CTFL-AcT Exam Dumps : ISTQB Certified Tester - Acceptance Testing (CT-AcT)

Equivalence Partitioning (EP) is a black-box test design technique that divides input data into valid and invalid partitions, where each partition is expected to exhibit similar behavior. In the context of acceptance testing, EP is especially effective because it helps validate whether a system behaves correctly for representative input ranges defined in the acceptance criteria.

Acceptance testing aims to confirm that the system meets business requirements and handles inputs as expected. EP allows the tester to cover a large input space using fewer test cases while maintaining a high level of effectiveness. It supports efficiency, broad coverage, and relevance to user expectations.

Other options are less suitable:

A. Static code analysis is a white-box technique, more relevant to unit or integration testing.

B. Input validation is an objective or activity, not a test design technique.

D. Defect-based testing is more diagnostic, used after failures or during exploratory testing — less structured for planned acceptance testing.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 2.4):

“Black-box techniques such as equivalence partitioning and boundary value analysis are suitable for deriving acceptance tests from user stories or business rules.”

UX task analysis focuses on understanding how users perform their tasks in real-world contexts. It captures not only the sequence of actions but also the surrounding environment — including physical conditions (light, noise), devices used, interruptions, and constraints. These external or environmental conditions become vital inputs to UX design decisions, helping teams adapt interfaces and workflows to user realities.

Option C is correct because it emphasizes this key aspect of UX task analysis: capturing external conditions that influence usability and system interaction.

Other options:

A focuses on user profiling, not task analysis.

B refers to business process modeling, which is more strategic and less user-context specific.

D refers to benchmarking or inspiration analysis — useful for design ideation but not task analysis.

Answer: C. External conditions are considered as input for subsequent design steps.

Beta testing is a form of external user acceptance testing where real users test the product in their environment before the official release. It helps identify issues that may not have been caught in internal testing and gather user feedback on functionality, usability, and performance in real-world conditions.

Option C is correct — the core goal of beta testing is to obtain user feedback in their actual usage context, providing insight into how the system performs outside of controlled environments.

Other options:

A: Test charters are used in exploratory testing, not typically in beta testing.

B: Incorrect — beta testing is not tied to the timing of user story development in Agile.

D: Incorrect — beta testing is performed by end users, not by internal team members like developers or business analysts.

Answer: C. Beta testing aims to obtain feedback from users in their context of use