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

Exploratory testing in Agile projects is a structured but unscripted testing approach where learning, test design, and execution occur simultaneously. Timeboxing is a key practice in managing exploratory testing sessions effectively.

A timebox is a fixed duration (e.g., 60–90 minutes) within which testers explore specific functionalities or risks. It encourages focus, documentation of findings, and prevents overrun or testing fatigue. After the session, testers often hold debriefs to review findings and determine next steps.

Option D is correct because timeboxing is essential for exploratory testing management.

Incorrect options:

A. Pair programming relates to development, not testing.

B. Refactoring is a development technique focused on improving code without changing behavior.

C. Planning poker is used in Agile for effort estimation, not directly related to exploratory testing.

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

“Exploratory testing is often conducted in time-boxed sessions, with a charter guiding the scope of the session.”

Acceptance testing primarily focuses on verifying whether a system meets agreed-upon requirements and satisfies the business and user needs. Quality attributes (also known as non-functional requirements) play a vital role in defining the completeness of the acceptance testing process.

Let’s analyze the options:

ii. Functional suitability — directly relates to whether the system provides the correct functions as per business needs. Essential in acceptance testing.

v. Security — ensures that the system is protected against unauthorized access or data breaches. Often critical for business stakeholders.

vii. Maintainability — reflects how easily the system can be modified. Relevant in acceptance if maintainability requirements are part of contractual criteria.

Thus, Option B (ii, v, vii) contains three attributes that are very relevant for acceptance testing.

Other options:

A includes vi (cognitive ability), which is not a standard ISO 25010 quality attribute.

C includes i (commercializability) — not a system quality attribute defined in ISO 25010.

D includes iii (viability) — more of a business or market consideration, not system testability.

Answer: B. ii, v and vii

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

Bi-directional traceability is a fundamental concept in requirements engineering and test management. It refers to the ability to trace:

Forward: From requirements/user stories to corresponding test cases (to ensure all requirements are covered).

Backward: From test cases to the requirements they validate (to ensure every test aligns with a requirement).

According to the ISTQB Certified Tester Foundation Level and Acceptance Testing syllabi, bi-directional traceability is essential to manage test coverage and ensure completeness. It allows project managers and product owners to assess whether all specified requirements/user stories have been covered by appropriate test cases, helping to identify any untested functionality.

This also supports impact analysis during change management — knowing which test cases will be affected by a change in a requirement.

Option B is correct because it precisely captures this benefit. While Option C refers to reviewing test cases against acceptance criteria (a valid review activity), the bi-directional traceability's key benefit from a management and quality assurance perspective is traceability for coverage.

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.