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

This user story is about a logged-in user measuring their blood sugar using a connected glucose meter and seeing the result quickly. The acceptance criterion specifies that the result should be displayed in less than four seconds.

Option B is correct because:

It starts with a valid GIVEN precondition (“I am logged in”).

The WHEN step matches the functionality described in the user story (blood sugar measurement using a connected device).

The THEN step explicitly includes the performance expectation (“less than 4 seconds”), aligning directly with the acceptance criterion.

Other options:

A is incorrect — while it mentions the correct functionality, “I am diabetic” is not a necessary system precondition.

C refers to blood pressure instead of blood sugar — mismatched with the user story.

D introduces additional functionality (alerts for hypo-/hyperglycemia), which is not part of the specified acceptance criteria.

Answer: B. GIVEN I am logged in on the system … THEN I can see the result … in less than 4 second

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

Effective test reporting should be tailored to the audience’s role and needs. Project managers are typically concerned with high-level progress, schedules, risks, and milestones. Progress trend charts (e.g., test execution over time, defect trends) provide insights into how the project is advancing and help identify delays or bottlenecks.

Option B is correct as it fits the informational needs of a project manager.

Other options:

A: Defect reports are too detailed for steering groups, which prefer strategic summaries or risk reports.

C: Pie charts may provide high-level summaries, but development teams usually need detailed defect or test result data.

D: System users (e.g., customers) are not responsible for project risks and would not benefit from test risk rankings.

Answer: B. Progress trend charts for the project manager