CTFL_Syll_4.0 Exam Dumps : ISTQB Certified Tester Foundation Level (CTFL) v4.0

Debugging activities typically include reproducing the failure, diagnosing the root cause, and fixing the cause of the failure. Adding new test cases, while important in the overall testing process, is not a direct part of debugging. Debugging focuses on understanding and correcting the issue that caused the failure, rather than expanding the test suite.

Comprehensive and Detailed Explanation From Exact Extract:

This is a classic application of theDecision Table Testingtechnique.

We are combining two conditions:

Purchase Volume, which has3 equivalence classes:

1 to 100 units → 0%

101 to 1000 units → 5%

More than 1000 units → 10%

Customer Type, which has2 categories:

Frequent Customer = YES → 5% extra

Frequent Customer = NO → 0%

This gives:

3 (bulk discount levels) × 2 (frequent customer options) = 6 unique decision rules

Each combination of these input conditions defines a separate test scenario with its own outcome.

“Decision table testing is used to identify the different combinations of inputs and their associated outputs. Each unique combination of input values defines a rule.”

(ISTQB CTFL Syllabus v4.0, Section 4.2.3 – Decision Table Testing, Page 40)

Thus,Option D (6 decision rules)is the correct answer.

ATDD stands for Acceptance Test-Driven Development, which is a collaborative approach to software development and testing, in which the acceptance criteria of a user story are defined and automated as executable tests before the implementation of the software system. ATDD tests are usually written in a Given-When-Then format, which describes the preconditions, the actions, and the expected outcomes of a test scenario. ATDD tests are intended to verify that the software system meets the expectations and the needs of the users and the stakeholders, as well as to provide feedback and guidance for the developers and the testers. Based on the given information, the ATDD test that is most likely to be written first is the one that corresponds to option B, which is:

Given the logged-in user is on the Change Password page When the user enters the correct current password, enters a valid new password (different from the last 5 passwords), and presses the Change Password button Then the user receives an email confirming that the password has been successfully changed

This ATDD test is most likely to be written first, because it covers the main functionality and the happy path of the user story, as well as the most important acceptance criterion [a]. It also verifies that the user can change the password with a valid new password that meets the criteria related to the length, the type of characters, and the history of the passwords, as specified in the acceptance criterion [c]. The other options are not likely to be written first, because they either cover less critical or less frequent scenarios, such as entering a wrong current password [d] or an invalid new password [e], or they are not related to the user story or the acceptance criteria at all, such as submitting a purchase order [d]. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles1

ISTQB® Glossary of Testing Terms v4.0, Acceptance Test-Driven Development, User Story, Acceptance Criterion, Given-When-Then2