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

Acceptance Test-Driven Development (ATDD) involves early collaboration between stakeholders to define acceptance criteria and tests before development begins. Using business process models in ATDD helps visualize user behavior, align test cases with real workflows, and serve as living documentation.

Option C is the least meaningful argument because:

Business process models abstractly describe workflows and decisions at a business level. While they help clarify requirements and detect requirement-related defects, they do not directly support detecting defects in the application code, which is typically the focus of unit and integration testing, not acceptance testing.

Let’s validate the other options:

A is a strong argument — process models clarify use cases for testers.

B is valid — graphical models help visualize test coverage directly.

D is true — as business process models evolve, they remain valuable artifacts aligned with current system behavior and requirements.

Answer: C. Business process models will make it easier to detect defects in the application code.

Performance testing evaluates how a system behaves under specific conditions, including load, stress, and endurance. Stress testing, in particular, involves pushing the system beyond its normal operational limits to identify breaking points.

Option B is correct because it describes a classic stress testing scenario: simulating users executing memory-intensive operations to evaluate system resilience and resource management.

Other options:

A describes usage profiles but is more aligned with load testing or configuration testing.

C refers to functional coverage, not performance-specific concerns.

D describes fuzz testing, which is used more for security or robustness testing than performance evaluation.

Answer: B. The system is stressed by simulating various users that perform memory-intensive tasks

Model-Based Testing (MBT) is a test design technique in which test cases are derived from a model that describes some aspects of the system’s behavior. In the context of acceptance testing, MBT can be used to generate high-level acceptance test cases automatically from business process models, use case diagrams, state models, or decision tables.

Option A is correct because MBT supports the systematic generation of acceptance test cases from these models, enabling better coverage of business rules and workflows while maintaining traceability to the requirements.

Other options:

B is close but slightly off: prioritization of acceptance tests in a priority-based approach depends on business value or stakeholder-defined priorities, not strictly on product risks.

C is incorrect. Risk-based testing relies on structured risk assessment, not just intuition or experience.

D is false. Black-box testing focuses on inputs and outputs without referencing the internal structure (such as function calls), which is characteristic of white-box testing.

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

“Model-based testing can be used to generate acceptance test cases systematically based on models representing business processes or system behavior.”

The medical scanner must be able to examine at least 50 patients per day. This requirement directly impacts hospital operations and service efficiency. If the scanner fails to meet performance requirements, such as processing speed or availability, it will affect the hospital’s ability to deliver services to patients — impacting schedules, patient flow, and ultimately the business goals of the hospital.

Option C is correct because it reflects the consequences of performance shortfalls from a business outcome perspective: failure to meet this requirement may result in financial loss, compliance issues, or customer dissatisfaction.

Other options:

A (User perspective) is involved, but the impact here is primarily operational/business.

B (Functional perspective) refers to whether the scanner has the correct features, not performance.

D (Technical perspective) is also relevant, but the business impact (e.g., service delivery) takes precedence in this case.

Answer: C. Business perspective

The relationship between business goals, business needs, and requirements is hierarchical and reflects increasing levels of specificity:

Business Goals: High-level strategic objectives.

Business Needs: Problems or opportunities that must be addressed to achieve those goals.

Requirements: Specific capabilities or conditions the system must satisfy to meet the needs.

Option B is correct because it accurately describes how these elements relate at different abstraction levels in the requirements hierarchy. This relationship is fundamental to business analysis and accepted by standards like BABOK and ISTQB.

Other options:

A is reversed — business goals usually precede and drive the elicitation of requirements.

C and D misrepresent the sequence — product requirements are derived from business goals and needs, not the other way around.

Answer: B. Business goals, business needs and requirements describe, at different levels of abstraction, what shall be achieved

Comprehensive Detailed Explanation (Approx. 200 words):

Acceptance criteria should focus on business-relevant outcomes that are specific, testable, and observable. In this user story, the goal is to validate that the registration functionality is available and behaves as expected.

Let's analyze each proposition:

i) “A registration form is displayed on the screen.”

→ Valid. It is observable, specific, and directly aligned with the user story.

ii) “The form is written in the Groovy language; the cursor is initially set on the ‘login’ field...”

→ Invalid as acceptance criteria. It contains implementation details (e.g., “Groovy language”) irrelevant to business stakeholders. Also, low-level UI behavior like cursor position is overly technical and not a business-driven criterion.

iii) “I cannot register myself if the login I choose is used by another player.”

→ Valid. It defines system behavior based on a business rule (unique login) and is testable.

iv) “After successful registration process I am informed about it by an e-mail.”

→ Valid. It describes a user-visible outcome after registration, which is observable and testable.

Correct answer: D. only i), iii), and iv) are well-written acceptance criteria.

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

“Acceptance criteria must describe the externally visible and verifiable system behavior, excluding implementation details.”

Defect reporting is a core responsibility of testers. When a test fails, the tester must document the observed behavior and how it differs from the expected behavior. This allows developers, analysts, and stakeholders to assess whether the issue is a defect, and if so, prioritize and fix it.

Option B is correct because it accurately describes the core responsibility of a tester when logging a defect: report the mismatch between actual and expected outcomes clearly and objectively.

Other options:

A refers to meetings, which are useful but not a replacement for clear defect reports.

C incorrectly assigns the role of defect routing to business analysts — this is typically handled by test or defect management tools.

D suggests the tester analyzes impact before reporting — which could delay the defect being logged and is not always the tester's role (impact analysis is often done collaboratively later).

Answer: B. Testers should provide accurate information regarding the difference between the expected test result and the actual result.

Poorly defined requirements are a leading cause of defects and project failure. According to the ISTQB CTFL Acceptance Testing Syllabus and IQBBA FL Syllabus, the quality of requirements plays a critical role in successful solution development and acceptance testing. Requirements must be clear, unambiguous, complete, and testable. When they are vague or ambiguous, stakeholders may interpret them differently, which can lead to incorrect implementations, inadequate testing, and ultimately rework or rejection during acceptance.

Option A is explicitly supported by the ISTQB Foundation Syllabus and IQBBA principles. In contrast:

Option B is incorrect because Agile lifecycles still place great emphasis on requirement engineering, even though requirements evolve iteratively.

Option C misrepresents INVEST: it is a guideline for writing good user stories but does not replace reviews or validation techniques.

Option D is risky and not endorsed by ISTQB. While testers may identify ambiguities, the correct approach is to clarify them with all relevant stakeholders, not make assumptions.

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

“Ambiguous, incomplete, or inconsistent requirements increase the risk of misunderstanding between stakeholders, leading to incorrect implementation and ineffective tests.”