iSQI Updated CTFL_Syll2018 Exam Questions and Answers by apollo

 Test objectives are specific goals or targets that define what testing activities should achieve or accomplish1. 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 testing1. Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes or defect corrections1. 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 testing1. An incident is any event occurring during testing that requires investigation1. This metric can indicate whether all defects have been identified and corrected at all levels of testing.

The fundamental test process is a generic model that describes the main activities and tasks involved in testing. The fundamental test process consists of five phases: planning and control, analysis and design, implementation and execution, evaluation of exit criteria and reporting, and test closure activities. Implementation and execution is the phase where test cases and test procedures are implemented according to test specifications and executed on the system or component under test using test tools or manual methods. Implementation and execution also involves verifying that the test environment set up is correct, which means ensuring that the test environment (such as hardware, software, network, data, etc.) is ready and suitable for testing the system or component under test. A detailed explanation of implementation and execution can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 19-21.

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.

To be based on an analysis of the structure of the component or system. White box testing techniques are based on the internal structure and code of the system, not on its specifications or functionality. White box testing techniques include statement coverage, decision coverage, branch coverage, path coverage, etc. White box testing techniques are usually performed at lower levels of testing, such as unit testing or component testing. A detailed explanation of white box testing techniques can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 68-74.