Free Practice Questions for iSQI CTFL-AcT Exam

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.

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.

Graphical representations of business processes, particularly using BPMN (Business Process Model and Notation), serve as a bridge between business stakeholders and testers. These models help visualize the steps a user or system goes through, making it easier to derive test cases.

Option C is correct because acceptance testing aims to validate the system’s behavior from the user or business perspective. Therefore, focusing on key user workflows (rather than exhaustive technical or exception paths) aligns with the purpose of acceptance testing: to ensure that the system meets agreed-upon business requirements.

Option A is incorrect because decision tables are part of DMN (Decision Model and Notation), not BPMN.

Option B is too rigid — not all alternative/error paths must be modeled in early acceptance testing unless they are critical to business rules.

Option D misapplies the standards — DMN is used to model business rules, not the complete business process.

Answer: C. For acceptance testing, graphical business process models should focus on the user workflows to be tested.

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.”