iSQI ISTQB Certified Tester - Acceptance Testing (CT-AcT) CTFL-AcT Exam Dumps: Updated Questions & Answers (October 2025)

Comprehensive Detailed Explanation:

According to the scenario described in the question, the business process for expense reimbursement includes two key timing constraints:

If the request is not processed within 7 days, an "ongoing" email is sent to the employee.

If the request is not completed within 30 days, the process is canceled and the employee is asked to resubmit the request.

However, in the BPMN model presented in the image, the second timing event (clock icon near "Approval in Progress") incorrectly shows 23 days instead of 30 days. This discrepancy misrepresents the actual business rule and violates the accuracy required in process modeling.

ISTQB Foundation Level Extension – Acceptance Testing syllabus and the Certified Tester Foundation Level Business Process Testing (CTFL-BAT) emphasize that a process model should correctly reflect the specified behavior, rules, and constraints of the business scenario. An incorrect timer can lead to miscommunication between stakeholders and incorrect automation or implementation logic.

Therefore, Option A is the most likely review comment since it directly points to this inconsistency in the model.

To determine the minimum number of test cases needed to cover:

All unique paths (without repeating loops) in the BPMN process model.

All decision rules (combinations) in the DMN decision table.

Let’s break it down:

BPMN Paths:

If the purchase order is not approved → process ends → 1 path

If approved:

Goods received → “Check of delivery” → Acceptance YES → Payment → 1 path

Goods received → “Check of delivery” → Acceptance NO → Discussion → End → 1 path

= Total distinct BPMN paths: 3

DMN Table:

There are 4 rules based on two inputs (Quality check and Quantity check):

Acceptable + Amount ok → Passed

Substandard + Amount ok → Failed

Acceptable + Amount incorrect → Failed

Substandard + Amount incorrect → Failed

You must execute 4 combinations to cover all decision rules.

To cover both all BPMN flows and all DMN rules, you need a minimum of 4 test cases (each using a different rule from the DMN table and associated BPMN path). Paths may overlap, but all rules must be exercised.

ISO/IEC 25010 defines two key quality models:

Product Quality Model (e.g., Usability, Security, Portability)

Quality in Use Model — which includes characteristics of the user’s experience when interacting with the product in a real-world context.

The four main characteristics of the Quality in Use model are:

Effectiveness

Efficiency

Satisfaction

Freedom from risk

Option A — Efficiency is one of the key Quality in Use characteristics, as it refers to the resources used to achieve goals with accuracy and completeness.

Other options:

B (Usability), C (Compatibility), and D (Portability) are characteristics of the Product Quality Model, not of Quality in Use.

Therefore, the correct answer, as per ISO 25010:2011, is:

Answer: A. Efficiency

Clear, complete, and testable requirements or user stories are critical for effective acceptance testing. Ambiguities or vague statements lead to differing interpretations by stakeholders, developers, and testers. This often results in software that doesn’t meet user expectations or in tests that fail to verify business needs correctly.

Option B is correct because it highlights the importance of precise requirements in both implementation and testing phases. Ambiguities can result in incorrect behavior, untestable features, or test cases that don’t align with business goals.

Other options:

A is risky — while testers may explore assumptions during exploratory testing, relying on assumptions rather than clarification increases risk.

C is incorrect — the INVEST mnemonic helps write better user stories, but it doesn’t replace review or validation processes.

D is false — Agile still values requirements engineering; it’s more collaborative and incremental, with the product owner playing a key role, not diminishing its importance.

Answer: B. Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing

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.

In BPMN models, additional annotations such as links to requirements, test data, or risks improve the value of the diagram for downstream stakeholders like testers. When BPMN tasks or flows are linked to known risks, testers can prioritize regression test cases accordingly — a key principle in risk-based testing.

Option D is correct because linking risks to business processes gives testers meaningful input for deciding which parts of the system require deeper or repeated testing.

Other options:

A: Priority links are useful, but less impactful than risk-based test selection.

B: Links to test equipment are not commonly embedded in process diagrams and are more relevant to hardware or system integration testing.

C: Linking to requirements helps traceability, but execution readiness is more closely tied to test cases and data than to BPMN.

Answer: D. Link to risks provide input to testers for selecting regression tests

An exploratory test charter is a high-level plan or mission statement for a time-boxed exploratory testing session. It guides what the tester should focus on during the session and may include the goal of the test, specific areas of the system under test, the risk or feature to explore, the type of persona to simulate (e.g., novice or expert user), and possibly known issues to watch out for.

Option A is correct because specifying a user persona (such as a novice user) helps the tester approach the system from that perspective. This supports the goal of exploratory testing: to simulate realistic usage and uncover issues that scripted tests might miss.

Option B is incorrect — although exploratory testing is adaptive, the charter is defined before the session starts, not elaborated during execution.

Option C is misleading — charters may refer to areas of interest, but not necessarily to a predefined list of activities.

Option D is incorrect — a test oracle (i.e., the mechanism for determining whether a result is correct) is not defined by the charter. It may exist already or be inferred from requirements, heuristics, or user expectations.

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

“Charters define the focus of exploratory testing sessions and may specify the tester’s role or perspective (e.g., novice user).”

In acceptance testing, testers execute test cases that are directly derived from user stories or requirements via their acceptance criteria. During execution, testers compare the actual outcome of the system with the expected result described in the acceptance criteria. If there's a mismatch (a deviation), it is documented as a defect or discrepancy.

This process is essential for validating that the system meets business needs. The tester’s role includes reporting clear, objective findings—not fixing the defect or deciding its severity (which might involve developers or business analysts).

Option A is incorrect: Business analysts may support testing, but execution is primarily a tester’s responsibility.

Option C is not fully correct: While developers may fix defects, assignment and triage follow a formal workflow and do not happen automatically.

Option D is incorrect: Business analysts don’t repeat test executions; this is the tester’s responsibility.

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

In acceptance testing, close collaboration between testers and business analysts ensures that test results are properly interpreted and aligned with business expectations.

A. Testers verify the effectiveness of corrective actions and document their verdict in the defect report — Correct. When a defect is resolved, testers retest the system and record whether the issue is fixed. This is a common testing activity during acceptance test execution.

E. Business analysts compare the test execution result to the acceptance criteria of the requirement / user story — Correct. This ensures the functionality fulfills business needs and determines whether the criteria have been met for acceptance.

Incorrect options:

B: Testers do record actual results, but not necessarily "in a defect" unless a defect is found.

C: Priority is usually assigned by business analysts or stakeholders, not testers alone.

D: Business analysts do consider the impact of changes, but evaluating development risks is more a joint task with architects or developers.

Answer: A and E