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

Statement coverage, also known as line coverage, is a metric used in white-box testing to measure the percentage of executable statements in the source code that have been executed by the test suite. Achieving a certain percentage of statement coverage means that an equivalent percentage of the executable statements in the code have been executed during testing.

For example, achieving 80% statement coverage indicates that 80% of the lines of code have been run through during the testing process. This metric helps in identifying parts of the code that have not been tested and may contain undetected defects.

It's important to note that achieving high statement coverage does not necessarily guarantee that all possible paths or scenarios within the code are tested, nor does it ensure the detection of all types of defects. Other coverage metrics, such as branch coverage or condition coverage, might also be necessary to achieve a more thorough testing process.

White-box testing, also known as structural testing, involves testing the internal structures or workings of an application, as opposed to its functionality (which is tested by black-box testing). The correct statement about white-box testing is that it helps find defects by measuring aspects such as statement coverage.

Statement Coverage: White-box testing techniques like statement coverage measure whether each statement in the code has been executed at least once. This helps ensure that all parts of the code are tested and can reveal defects in areas that might not be reached by black-box testing alone​​.

Other statements are less accurate in the context of white-box testing:

Specifications being vague: White-box testing is code-focused, not requirement-focused. If specifications are vague, it affects both white-box and black-box testing. The main advantage of white-box testing is that it allows testers to create tests based on the code's structure and logic​​.

Requirements-based coverage: This is typically associated with black-box testing, which derives tests from specifications and requirements. White-box testing, on the other hand, derives tests from the code itself​​.

Focus on defects rather than failures: Both white-box and black-box testing aim to identify defects, but white-box testing does this through code coverage and examining the code paths directly. It does not focus exclusively on defects rather than failures; it is just another method to identify potential issues​​.

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.