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

Collaboration between business analysts and testers is critical in Agile and acceptance testing environments. One of the most effective areas of cooperation is the joint development and review of acceptance criteria for user stories. This ensures that criteria are testable, clearly defined, and aligned with stakeholder expectations.

Option B is correct because creating acceptance criteria is where both business analysts (who understand the business needs) and testers (who ensure testability and clarity) contribute effectively.

Other options:

A (Business needs assessment) is typically a responsibility of business analysts, not a joint activity with testers.

C (Review of risk to prioritize acceptance tests) is a valuable activity but comes after criteria are defined. While it can be collaborative, it's more specific to test planning.

D (Definition of Beta Testing sessions) is less relevant to ongoing collaborative work between testers and BAs — this involves users and release planning.

Answer: B. Development of acceptance criteria for user stories

Comprehensive Detailed Explanation (Approx. 200 words):

Acceptance criteria are an essential part of requirements engineering and test design. According to the ISTQB CTFL Acceptance Testing Syllabus, acceptance criteria are defined as a set of statements that specify what must be true for a system, feature, or user story to be considered acceptable to stakeholders. These criteria are used as the basis for developing acceptance test cases and help bridge the communication between stakeholders, business analysts, developers, and testers.

They are not exclusive to Agile frameworks (contrary to option A); while common in Agile (e.g., as part of a user story), they are equally valuable in traditional lifecycles. Option B is incorrect because testers are encouraged to collaborate in defining acceptance criteria early to ensure testability and clarity. Option C incorrectly states that acceptance criteria replace acceptance tests in ATDD (Acceptance Test-Driven Development). In fact, acceptance criteria are transformed into acceptance tests during ATDD.

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

“Acceptance criteria describe the conditions under which a requirement, user story, or business process is considered successfully implemented. They provide the foundation for acceptance testing and serve as input to test case development.”

Therefore, option D is the most accurate.

In Gherkin syntax (Given-When-Then), the purpose is to describe system behavior in a way that’s understandable to all stakeholders. Test steps should focus on user intentions and observable results — not UI implementation details — to ensure maintainability and abstraction.

Line 3 ("click 'Buy Tickets' button") refers explicitly to a UI element, which should generally be avoided in acceptance tests. Instead, it could say "I request to buy tickets."

Line 7 ("I should provide my personal data") is describing an action the user must take, not an outcome or result. In a Gherkin “Then” step, we expect an observable system response, not further user interaction.

Option C identifies both of these review concerns correctly.

Other options:

A includes an incorrect comment about line 4 ("quantity should not be set") — setting a value is acceptable.

B is false — the test case has reviewable issues.

D might be valid in a different context (e.g., boundary tests), but that’s not a flaw in the existing scenario.

Answer: C. Line 3 refers to an element of the user interface, which is to be avoided and line 7 is an action and not a result