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

Let’s analyze the DMN table shown in the image:

Rule 1: If weight ≤15, size ≤50, and distance ≤10 → use Normal bicycle

Rule 2: If weight is between 15 and 60 kg, size ≤150, and distance ≤25 → use Electric cargo bike

Rule 3: Otherwise → use Electric van

Now consider the options:

A: Incorrect — parcel size is not the only determining factor for using electric vans; it's about weight, size, and distance combined.

B: Incorrect — normal bicycles are used only when weight ≤15 kg, size ≤50 cm, and distance ≤10 km — so not just “short trips.”

C: Incorrect — electric cargo bikes are explicitly used for short trips (≤25 km), per Rule 2.

D: Correct — based on the rules, any weight above 15 kg (and up to 60 kg) results in the use of electric cargo bikes. So if weight >50 kg (but ≤60), cargo bike is still used under the conditions of Rule 2.

Therefore, the most consistent interpretation of the decision model is:

Answer: D. When the weight of the parcel exceeds 50kg then the electric cargo bike is necessarily used

Gherkin is a structured language used in Behavior-Driven Development (BDD) to define test cases in a clear, business-readable format. It follows the GIVEN-WHEN-THEN structure:

GIVEN describes the precondition (system’s state before the action).

WHEN describes the action/event.

THEN describes the expected result or outcome.

Analyzing the phrases:

ii) “The elevator is on the Ground Floor” is a precondition — fits GIVEN.

i) “The total weight of passengers is greater than 200 kg” is an action or state change — fits WHEN.

vi) “A message ‘too many passengers’ is displayed on the screen” is the expected outcome — fits THEN.

Thus, Option A correctly maps these elements to form a well-structured Gherkin scenario.

Other options are incorrect because:

Option B misplaces an expected outcome as an action.

Option C misrepresents the order — “login” isn’t a precondition.

Option D introduces two THEN elements and violates the typical Gherkin structure.

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

“Gherkin test cases use GIVEN-WHEN-THEN structures to make the behavior of the system under test understandable by all stakeholders.”

Ensuring traceability between requirements (user stories) and test cases is a cornerstone of quality assurance in acceptance testing. It confirms that all business needs are covered by corresponding tests and helps assess the impact of changes. Traceability matrices or tools are used to track these links throughout the lifecycle.

Option B is correct because regularly verifying and updating traceability ensures that acceptance test coverage remains aligned with evolving requirements — a best practice in quality assurance.

Other options:

A (review of source code) is a white-box technique, more suitable for unit or integration testing.

C (checklist-based verification of requirements) is useful but focuses on requirement quality, not directly on testing activities.

D (eye tracking) is a usability evaluation technique and not standard for verifying test case feasibility.

Answer: B. Verification of the traceability between user stories and test cases to make sure it is up to date.

Acceptance criteria describe what the system must do to fulfill a requirement from the user or business perspective. They must be observable, testable, and relevant to the business outcome or expected behavior.

In this scenario, the user story is about monitoring blood pressure and receiving alerts for excessive pressure. The acceptance criteria should focus on system behavior, thresholds, and how alerts are triggered based on user settings.

Option D is not a good acceptance criterion because:

It specifies a technical implementation detail (JavaScript framework), which is not the concern of acceptance testing.

Acceptance criteria should not prescribe how the system is built, but what it must do from a business or user point of view.

Other options (A, B, and C) all reflect testable and behavior-focused outcomes linked to the user story’s goal.

Answer: D. The system should be developed using JavaScript framework to allow fast response times

Test reports summarize the results of test execution and are often used by stakeholders, including business owners and release managers, to make informed decisions about whether to release a product. If these reports are ambiguous, incomplete, or inaccurate, the decisions based on them could be flawed, leading to reputational damage, customer dissatisfaction, or regulatory issues.

Option A is correct because it highlights the risk of basing critical go/no-go decisions on poor-quality reporting.

Other options:

B describes a problem with test case implementation, not test reporting.

C mentions public perception, which might be influenced by report quality, but it is secondary to the internal decision-making purpose.

D refers to human error during test execution or design, not the purpose of reviewing test reports.

Answer: A. If the test reports are unclear or incomplete, the decision to release the product can be based on non-reliable information

In BDD (Behavior-Driven Development) and ATDD (Acceptance Test-Driven Development), “living documentation” refers to executable acceptance criteria that are kept up to date throughout development. These acceptance tests are written in natural, structured language (like Gherkin's Given-When-Then) and are linked directly to business requirements.

Option A is correct — “living documentation” bridges the gap between business and development by keeping requirements executable, relevant, and up to date.

Other options:

B is misleading — visual ATDD may use process models, but this is not a defining characteristic of BDD or ATDD.

C is true in part — BDD scenarios often use Given-When-Then, but this by itself is not the most defining statement when comparing options.

D is incorrect — ATDD and BDD support collaboration, but they do not expect business analysts to write code or automation scripts.

Answer: A. The concept of "living documentation" means that business requirements become executable

The goal here is to achieve full decision coverage (also known as branch coverage), which means each decision point in the process must evaluate to both TRUE and FALSE at least once during testing.

From the BPMN ATM withdrawal model, we identify two key decisions:

Is the balance ≥ $100?

If yes, is receipt = YES?

To achieve full decision coverage:

One test must evaluate decision 1 as TRUE and another as FALSE.

If decision 1 is TRUE, then decision 2 must be exercised both ways (receipt = YES and NO), but for minimal decision coverage, one path through decision 2 is enough.

Analyzing test cases:

Test 1 (balance = $100, receipt = YES): decision 1 = TRUE, decision 2 = TRUE

Test 2 (balance = $99): decision 1 = FALSE

These two tests ensure:

Decision 1 evaluated TRUE (Test 1) and FALSE (Test 2)

Decision 2 evaluated at least once (receipt = YES in Test 1)

Thus, Test 1 and Test 2 form the minimal set for full decision coverage.

Other options:

C and D are redundant for the minimal set.

A includes an extra test not needed for minimal decision coverage.

Answer: B. Test 1, Test 2