Vce CTFL-AcT Questions Latest

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

Performance testing assesses how a system behaves under specific conditions, typically focusing on responsiveness, stability, and resource usage. The type of performance test depends on the workload model:

Load testing evaluates performance under expected peak usage.

Stress testing pushes the system beyond its capacity to assess limits.

Endurance/stability testing checks for performance degradation over extended periods.

Option A correctly describes that performance test types are determined by the workload simulation strategy.

Other options:

B confuses performance with security testing — malicious attack robustness is a security focus, not performance.

C is partly correct but less comprehensive than A. While testing should simulate realistic conditions, categorization into stress/load/endurance is better aligned with workload modeling.

D is misleading — performance tests validate systems against performance requirements; they are not primarily used to define them.

Answer: A. Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.

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

Comprehensive Detailed Explanation (Approx. 200 words):

Acceptance criteria are an essential part of requirements engineering and test design. According to the ISTQB CTFL Acceptance Testing Syllabus, acceptance criteria are defined as a set of statements that specify what must be true for a system, feature, or user story to be considered acceptable to stakeholders. These criteria are used as the basis for developing acceptance test cases and help bridge the communication between stakeholders, business analysts, developers, and testers.

They are not exclusive to Agile frameworks (contrary to option A); while common in Agile (e.g., as part of a user story), they are equally valuable in traditional lifecycles. Option B is incorrect because testers are encouraged to collaborate in defining acceptance criteria early to ensure testability and clarity. Option C incorrectly states that acceptance criteria replace acceptance tests in ATDD (Acceptance Test-Driven Development). In fact, acceptance criteria are transformed into acceptance tests during ATDD.

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

“Acceptance criteria describe the conditions under which a requirement, user story, or business process is considered successfully implemented. They provide the foundation for acceptance testing and serve as input to test case development.”

Therefore, option D is the most accurate.