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

Decision testing is a white box (structure-based) test case design technique1. White box (structure-based) test case design techniques are techniques that use the structure or logic of the source code as a test basis to derive test cases and measure test coverage1. Decision testing is a technique that uses decisions (or branches) in the source code as a test basis to measure the coverage achieved by a test suite1. A decision (or branch) is a point in the source code where the control flow can take two or more alternative paths based on a condition1. Decision testing requires every decision (or branch) in the source code to take both true and false outcomes at least once by a test suite1. Therefore, decision testing is a white box (structure-based) test case design technique.

Functional and structural tests are alternative test types that may be used separately or together at B. All test levels. Functional testing is a type of testing that verifies the functionality of the system or component under test against its requirements or specifications. Functional testing focuses on what the system or component does, not how it does it. Structural testing is a type of testing that verifies the structure or code of the system or component under test. Structural testing focuses on how the system or component does it, not what it does. Functional and structural testing can be used separately or together at any test level, such as unit testing, integration testing, system testing, acceptance testing, etc. Functional and structural testing can complement each other by providing different perspectives and coverage of the system or component under test. A detailed explanation of functional and structural testing can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 25-26.

Functional and structural testing can both be applied at all test levels, from component testing to acceptance testing1 . Functional testing verifies whether the software meets the specified requirements and user expectations, while structural testing verifies whether the software meets the specified design and code standards1 . Both types of testing can be useful at any stage of the software development life cycle, depending on the test objectives and scope1 . The other options are incorrect, because they limit the application of functional and structural testing to certain test levels only.