Download Full Version CTFL_Syll2018 iSQI Exam

Configuration management is related to ensuring the integrity of the testware, as it is a process that controls and documents changes to test items, test cases, test data, test scripts, test results, and test documentation throughout the testing lifecycle. The other options are not related to ensuring the integrity of the testware, but to other aspects of testing such as test execution, test environment setup, and test planning.

References: Section 4.1, Section 4.2

100% branch coverage means 100% statement coverage, but not vice-versa. Branch coverage is a stronger criterion than statement coverage, as it requires that every possible outcome of each decision point is executed at least once. Statement coverage only requires that every executable statement is executed at least once1 explains this as follows:

Branch Coverage (also known as Decision Coverage) measures which possible branches in flow control structures are followed. Branch Coverage is a testing method, which aims to ensure that each one of the possible branch from each decision point is executed at least once and thereby ensuring that all reachable code is executed.

Statement Coverage measures the number of statements in the source code that are executed during the test. Statement Coverage is a metric, which is used to calculate and measure the number of statements in the source code which have been executed during testing.

B, C, and D are false statements. 100% statement coverage does not mean 100% branch coverage (B), as there may be some branches that are not covered by the test cases. 100% branch coverage does not mean 100% statement coverage and vice-versa ©, as branch coverage implies statement coverage but not the other way around. It is possible to achieve 100% statement coverage (D), but it may not be feasible or cost-effective for some systems.

The correct answer is A, as it states that the Wideband Delphi estimation technique is an example of the expert-based approach. The Wideband Delphi estimation technique is a method of estimating testing effort or duration by using a structured group process that involves multiple experts2. The experts provide their estimates independently and anonymously, then compare and discuss them until they reach a consensus2. This technique is an example of the expert-based approach, which is an approach that relies on the knowledge and experience of experts to estimate testing activities2. Option B is incorrect, as it states that the Wideband Delphi estimation technique is an example of the metrics-based approach. The metrics-based approach is an approach that uses historical data and mathematical formulas to estimate testing activities2. This approach does not involve experts or group processes. Option C is incorrect, as it states that burndown charts used in Agile development is an example of the expert-based approach. Burndown charts are graphical tools that show the amount of work remaining versus time in an Agile project2. They are used to monitor and control testing progress and quality. They are not examples of the expert-based approach, as they do not rely on experts’ opinions or estimates. Option D is incorrect, as it states that burndown charts used in Agile development is an example of the risk-based approach. The risk-based approach is an approach that uses risk analysis to prioritize and estimate testing activities2. This approach involves identifying and assessing risks based on their likelihood and impact. It does not involve burndown charts or Agile development. References: 2, Section 2.6

Component integration testing is the process of testing the interactions between different components of a system. It should always be done before system testing, which is the process of testing the system as a whole. Integration testing can reveal defects in the interfaces and interactions between components, which can affect the functionality and performance of the system. System testing can reveal defects in the system requirements, design, and behavior, which can affect the quality and usability of the system. Therefore, it is logical to perform integration testing before system testing, to ensure that the components work together correctly before testing the system as a whole.

References: Certified Tester Foundation Level Syllabus, Section 5.1.2 and 5.2.2