CTFL_Syll2018 Exam Dumps : ISTQB Certified Tester Foundation Level (Syllabus 2018)

The correct answer is B, as it achieves the highest equivalence partition coverage. Equivalence partitioning is a black-box test technique that divides the input domain into partitions of equivalent data from which test cases can be derived1. In this case, the input domain is the numerical grades, and the partitions are the ranges of grades that correspond to different letter grades. Option B covers all five partitions, as it includes test inputs from each range. Option A covers only four partitions, as it does not include any test input from the range above 89. Option C covers only three partitions, as it does not include any test input from the ranges above 79 and below 60. Option D covers only two partitions, as it does not include any test input from the ranges below 79. References: 1, Section 4.2.3

For the code fragment given below, one test case is required for statement coverage and two test cases are required for branch coverage. Statement coverage requires that every executable statement in the code is executed at least once. Branch coverage requires that every possible outcome of each decision point in the code is executed at least once. The following table shows how to achieve statement and branch coverage for the code fragment:

Test Case

Input

Output

Statement Coverage

Branch Coverage

1

x = 3

y = 9

S1, S2, S3

T1 = true

2

x = 5

y = 25

S1, S2

T1 = false

As shown in the table, test case 1 covers all three statements (S1, S2, S3) in the code fragment, achieving 100% statement coverage. Test case 2 covers only two statements (S1, S2) in the code fragment, but it exercises a different outcome of the decision point T1 (if x < 4), achieving 100% branch coverage.

The statement that best defines static techniques is D. Manual examination and automated analysis of code or project documentation. Static techniques are techniques that analyze the code or other software artifacts (such as requirements, specifications, designs, models, test cases, etc.) without executing them, and provide information about their quality, defects, complexity, maintainability, etc. Static techniques can be performed manually or automatically by using tools or methods such as reviews, inspections, walkthroughs, checklists, standards, guidelines, static analysis tools, code metrics tools, etc. Static techniques can help to improve the quality and consistency of code or other software artifacts throughout the software development life cycle and reduce the cost and effort of testing and debugging. A detailed explanation of static techniques can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 27-34.