CTFL-AcT Exam Dumps - iSQI ISTQB Foundation Level Questions and Answers

The best Gherkin-style acceptance tests are business-oriented, behavior-driven, and avoid unnecessary technical or UI details. They describe actions in a way stakeholders can understand, focusing on system behavior rather than implementation mechanics.

Option A follows Gherkin conventions:

GIVEN clearly describes the system state (account balances).

WHEN describes a user action (transferring funds).

THEN describes a verifiable outcome (account balances updated correctly).

Option B includes unnecessary UI actions like clicking buttons or field names, which are implementation-specific and violate the abstraction level expected of acceptance tests.

Option C uses appropriate structure but introduces incorrect balances in the THEN step (possibly a typo; $4500 on X is wrong if funds were transferred from Y to X).

Option D uses improper syntax — WHEN is misused as another GIVEN, and THEN describes a computation rather than a system behavior.

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

“Acceptance criteria in BDD are best captured through Gherkin scenarios that are understandable by business stakeholders and focus on expected outcomes, not implementation details.”

==================

According to ISO/IEC 25010:2011, the “Quality in Use” model includes characteristics that measure the system’s impact on stakeholders during actual usage in a specific context.

The four main characteristics of Quality in Use are:

Effectiveness

Efficiency

Satisfaction

Freedom from Risk

Option C is correct because “Satisfaction” is one of the core quality-in-use characteristics and refers to the degree to which user needs are fulfilled in context.

Other options:

A (User experience) is a broader term not formally defined as a Quality in Use characteristic in ISO 25010.

B (Security) is part of the product quality model, not quality in use.

D (Freedom of interference) is not a defined term in ISO 25010; it may be a misstatement of "freedom from risk."

Answer: C. Satisfaction

In ISTQB Acceptance Testing context, the process of refining requirements or user stories into acceptance criteria plays a crucial role in defining clear, testable conditions. These acceptance criteria act as the basis for deriving test conditions, which are in turn used to design acceptance test cases.

According to the ISTQB Foundation Level Acceptance Testing syllabus:

“Acceptance criteria are refined expressions of business requirements, and they help to determine the scope and intent of acceptance tests. These criteria are used to derive test conditions and guide the development of test cases.”

This alignment ensures that the delivered software meets the expectations set out in the requirements and satisfies the user needs. Acceptance tests are typically written from the user’s perspective and are focused on verifying that the system behaves correctly in realistic business scenarios.

Option B is correct because it explicitly describes this logical and procedural relationship between user stories, acceptance criteria, and acceptance tests.

Other options are incorrect or misleading:

A is incorrect: reviewing requirements does not eliminate the need for dynamic testing.

C is incorrect: code coverage is more relevant for unit or system-level testing, not acceptance testing.

D is incorrect: exploratory testing is a valuable supplement but does not replace the need to verify acceptance criteria.

Traceability is a key principle in requirements and test management. It ensures that all features, requirements, and tests are linked and accounted for. Including traceability to user stories in BPMN diagrams or DMN tables supports transparency, auditability, and maintenance.

Option B is correct because embedding or referencing traceability information within business models improves communication across stakeholders, ensures proper test coverage, and helps during change impact analysis.

Let’s evaluate other options:

Option A is incorrect. Trying to place all model elements in one diagram can lead to cluttered and unreadable models.

Option C is misleading. While separation of concerns is useful, traceability (links to requirements, risks) should be integrated or closely accessible from the models.

Option D is incorrect. Acceptance testers should be involved early to collaborate and review models. Waiting until models are finalized contradicts agile and ATDD principles.

Answer: B. BPMN diagrams and DMN tables should include information such as traceability to user stories.