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.

The statement that BEST describes when test planning should be performed is D. Test planning is performed continuously in all life cycle processes and activities. Test planning is the process of defining the objectives, scope, approach, resources, schedule, risks, and deliverables for testing activities. Test planning is not a one-time activity that is done only at the beginning of the life cycle or at each test level. Test planning is a continuous activity that is done throughout the life cycle in all processes and activities that involve testing. Test planning should be aligned with the development process and should be updated regularly to reflect any changes or feedback from previous testing activities. Test planning should also consider different levels of testing (such as unit testing, integration testing, system testing, acceptance testing, etc.) and different types of testing (such as functional testing, non-functional testing, regression testing, etc.). A detailed explanation of test planning can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 13-15.

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.

Experience-based test design techniques are techniques that use the skill, intuition, and experience of testers to derive test cases, using error guessing and exploratory testing 1 .  Error guessing is a technique that uses common sense and previous experience to guess where defects might occur in a system 1 .  Exploratory testing is an approach that involves simultaneous learning, test design, and test execution 1 .  Experience-based test design techniques are typically used when there is insufficient information or time to apply other more forma l techniques 1 . They do not use decision tables, identify the structure of the system or software, or establish traceability from test conditions back to the specifications and requirements.

  Test objectives are specific goals or targets that define what testing activities should achieve or accomplish 1 . Test objectives for systems testing of a safety critical system include completion of all outstanding defect correction. Regression testing is required following defect correction at all test levels. Therefore, to determine whether this test objective has been met, two metrics that would be most suitable are:

Regression tests run and passed in systems testing: This metric measures how many regression tests have been executed and passed in systems testing 1 .  Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes or defect corrections 1 . This metric can indicate whether all outstanding defect corrections have been completed and verified in systems testing.

Incidents raised and closed at all levels of testing: This metric measures how many incidents have been reported and resolved at all levels of testing 1 .  An incident is any event occurring during testing that requires investigation 1 . This metric can indicate whether all defects have been identified and corrected at all levels of testing.

 These are some of the factors that should be considered to determine whether enough testing has been performed. The exit criteria define the specific goals and requirements for testing completion. The budget limits the resources and time available for testing. The product’s risk profile indicates the areas of highest priority and impact for testing. Sufficient details of the system status allow decisions on whether further testing is needed or not. The other options are not relevant factors for determining enough testing.

Coverage of code, schedule, estimates of defect density. Exit criteria are the conditions that must be met before testing can be completed and the system can be released. Exit criteria can be based on factors such as coverage of code or requirements, schedule or budget constraints, estimates of defect density or severity, etc. Exit criteria help to determine when to stop testing and evaluate the quality of the system. A detailed explanation of exit criteria can be found in  A Study Guide to the ISTQB® Foundation Level 2018 Syllabus , pages 15-16 1 .

Decision testing is a white box (structure-based) test case design t echnique 1 .  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 coverage 1 .  Decision testing is a technique that uses decisi ons (or branches) in the source code as a test basis to measure the coverage achieved by a test suite 1 .  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 condition 1 .  Deci sion testing requires every decision (or branch) in the source code to take both true and false outcomes at least once by a test suite 1 . Therefore, decision testing is a white box (structure-based) test case design technique.

UAT stands for user acceptance testing, which is a type of testing t hat verifies that the software product meets the acceptance criteria and expectations of the end users or customers 1 .  A UAT specification is a document that defines the scope, objectives, approach, and criteria for UAT 1 .  Testers should be involve d in reviewing a UAT specification at any time before UAT begins, as this can help to ensure that the UAT specification is clear, complete, consistent, testable, and aligned with the user requirements 1 .  Testers can also provide feedback and suggestion s to improve the UAT specification and avoid potential issues or conflicts during UAT execution 1 . Therefore, testers should be involved in reviewing a UAT specification at any time before UAT begins.