The correct answer is D, as DT1 and DT4 would achieve full coverage of the full decision table when combined with the test cases that have already been generated for rules 1 and 4.  Decision table testi ng is a black-box test technique that uses a table to show combinations of inputs and their associated outputs 1 . In this case, the inputs are the account type, the amount entered, and the expected result. The outputs are the actions taken by the ATM system. The decision table has eight rules, each corresponding to a possible combination of inputs and outputs. The test cases that have already been generated for rules 1 and 4 are:

TC1: Account = Checking, Amount = $600, Expected Result = Process the transaction

TC4: Account = Savings, Amount = Not entered, Expected Result = Generate an error message

The additional test cases are:

DT1: Account = Checking, Amount = Not entered, Expected Result = Generate an error message

DT2: Account = Savings, Amount = $100, Expected Result = Process the transaction

DT3: Account = Checking, Amount = $100, Expected Result = Process the transaction

DT4: Account = Savings, Amount = $600, Expected Result = Generate an error message

To achieve full coverage of the full decision table, two more test cases are needed that cover the remaining six rules. DT1 and DT4 cover these rules, as shown in the table below:

Therefore, option D is the correct answer.  Options A, B, and C are incorrect, as they do not cover all the rules in the decision table. References:  1 , Section 4.2.5

According to the syllabus, use case testing is a technique that tests the functionality of a system using scenarios based on use cases. A use case is a description of how an actor interacts with a system to achieve a goal. A use case defines the expected behaviour and possible variations of the system under test. The answer A is correct because test cases are designed to exercise the defined behaviours of the use case and its variations. The other answers are incorrect because they are not true statements about use case testing. There can be multiple test cases for each use case, depending on the complexity and variations of the use case. Test cases can be derived from other sources besides activity diagrams, such as textual descriptions or flow charts. It is possible to measure use case test coverage by comparing the number of executed test cases with the number of defined test cases for each use case.

References:  Certified Te ster Foundation Level Syllabus , Section 4.5.1, page 49-50.

  To ensure that users can n avigate to all fields on the screen does not reflect structural testing, but rather functional testing or usability testing 1  .  Structural testing verifies whether the software meets the specified design and code standards by measuring aspects such as code coverage , complexity, or coupling 1  . The other options reflect structural testing at different levels of granularity.  Option A reflects structural testing at the system level by testing all paths that users could take through the screen menu system 1  .  Option B reflects structural testing at the component level by ensuring that 100% decision coverage is achieved for each system component 1  .  Option C reflects structural testing at the component integration level by testing al l branches of component calls within the application call graph

Incorrect interface specifications are most likely to be found by a review during static testing. A review is a type of static testing technique that involves a manual examination of a work product by one or more individuals who follow a defined process. A review can be applied to any work product, such as requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. A review can help find defects and improve the quality of any work product at any stage of the software development lifecycle. Incorrect interface specifications are defects that affect the definition and communication of the interfaces between components or systems. These defects can be detected by reviewing the interface specifications document and comparing it with the requirements and design specifications.

References:  Certified Tester Foundation Level Syllabus , Section 3.2.1

According to the syllabus, verification is the process of evaluating a product or component to determine whether it satisfies its specified requirements. Validation is the process of evaluating a product or component to determine whether it fulfills its intended use and user expectations. Verification answers the question “Are we building the product right?” while validation answers the question “Are we building the right product?” Both verification and validation involve providing objective evidence, which means factual, unbiased, and observable information that supports the evaluation. The answer D is correct because it best distinguishes the terms “validation” and “verification”. The other answers are incorrect because they either confuse the terms “validation” and “verification” or use subjective evidence, which means personal, biased, or unobservable information that does not support the evaluation.

References: [Certified Tester Foundation Level Syllabus], Section 1.2.1, page 10-11.

Gaining confidence about the level of the system’s quality can be a common objective of testing, because testing can provide information about how well the system meets its specified requirements and user expectations, and how many defects have been found and fixed in the system.

Error, fault, failure is the option that describes the causal chain in the correct sequence 1  .  The causal chain is a model that explains how defe cts are introduced and manifested in software 1  .  An error is a human action or decision that produces an incorrect re sult 1  .  A fault is a defect in the software caused by an error 1  .  A failur e is an incorrect behaviour of the software caused by a fault 1  . The other options do not describe the causal chain in the correct sequence. Option B uses synonyms for error (mistake), fault (bug), and failure (defect), but does not follow the correct order. Option C uses synonyms for error (mistake) and fault (failure), but does not follow the correct order and confuses fault with failure. Option D uses synonyms for fault (bug) and error (error), but does not follow the correct order and confuses failure with error.

The statement that use cases are normally derived from decision tables is not true. Decision tables are a technique to represent complex logical conditions in a tabular form, where each column represents a possible combination of conditions and actions. Use cases are a technique to describe how a system interacts with one or more actors (users or other systems) to achieve a specific goal. Use cases are not derived from decision tables, but from the requirements and the user’s perspective of the system.

References: [Certified Tester Foundation Level Syllabus], Section 4.5.2 and 4.3.2

Explanation of Correct Answer: Decision table testing is a test design technique that can be used for effectively testing system requirements consisting of logical conditions. Decision table testing is based on the idea that the system behavior can be represented by a table, where each column corresponds to a possible combination of inputs and each row corresponds to the expected outputs for that combination. Decision table testing helps to identify and cover all possible scenarios and outcomes for a given requirement12.

References: 1: Certified Tester Foundation Level Syllabus, Version 2018 v3.1.1, Section 4.3.2 2: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, Chapter 4, Section 4.3.2

Testing support tools are software tools that assist testers in performing testing activities, such as test management, test design, test execution, test evaluation, and defect management 1 .  According to the ISTQB syllabus, some typical targets of testing support tools are to automate activities that require significant resources when done manually, automate activities that cannot be executed manually, and automate repetitive tasks 1 .  Automating repetitive inspections is not a typical target of testing support tools, as inspections are static testing techniques that involve human review and analysis of software artifacts 1 .