Statement testingaims to executeevery executable statementin the source code at least once.
* (D) is correctas statement testing ensuresmaximum statement execution.
* (A) describes branch testing, which focuses on flow transfers.
* (B) and (C) incorrectly mix decision testing and branch testing concepts.
Reference:ISTQB CTFL v4.0 Syllabus, Section 4.3.1 - Statement Testing

This answer is correct because the whole-team approach is a way of working in agile projects where all team members share the responsibility for the quality of the product, and collaborate on delivering value to the customer. The whole-team approach involves testers, developers, business analysts, product owners, and other stakeholders in planning, designing, developing, testing, and delivering the product. The whole-team approach fosters communication, feedback, learning, and continuous improvement within the team. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section
3.1.1.1

A new navigation system compared with a previous system is the most suitable application for testing by use cases, because it involves a high level of interaction between the user and the system, and the expected behavior and outcomes of the system are based on the user's needs and goals. Use cases can help to specify the functional requirements of the new navigation system, such as the ability to enter a destination, select a route, follow the directions, receive alerts, etc. Use cases can also help to compare the accuracy and usability of the new system with the previous system, by defining the success and failure scenarios, the preconditions and postconditions, and the alternative flows of each use case. Use cases can also help to design and execute test cases that cover the main and exceptional paths of each use case, and to verify the satisfaction of the user's expectations.
The other options are not the most suitable applications for testing by use cases, because they do not involve a high level of interaction between the user and the system, or the expected behavior and outcomes of the system are not based on the user's needs and goals. A billing system used to calculate monthly charge based on a large number of subscriber parameters is more suitable for testing by data-driven testing, which is a technique for testing the functionality and performance of a system or component by using a large set of input and output data. The ability of an antivirus package to detect and quarantine a new threat is more suitable for testing by exploratory testing, which is a technique for testing the functionality and security of a system or component by using an informal and flexible approach, based on the tester's experience and intuition. The suitability and performance of a multimedia (audio video based) system to a new operating system is more suitable for testing by compatibility testing, which is a technique for testing the functionality and performance of a system or component by using different hardware, software, or network environments. References = CTFL 4.0 Syllabus, Section 3.1.1, page 28-29; Section 4.1.1, page 44-45; Section 4.2.1, page 47-48.

A defect report should contain relevant details to help developersreproduce and fix the defect efficiently.
The essential elements include:
* Test object & environment (A)- To ensure reproducibility.
* Title & summary (B)- For quick identification.
* Expected vs. actual results (D)- To describe the discrepancy.
Thestructure of the test team (C)is irrelevant for defect tracking and resolution.
Reference:ISTQB CTFL v4.0 Syllabus, Section 5.5 - Defect Management

Statement coverage, also known as line coverage, is a metric used in white-box testing to measure the percentage of executable statements in the source code that have been executed by the test suite. Achieving a certain percentage of statement coverage means that an equivalent percentage of the executable statements in the code have been executed during testing.
For example, achieving 80% statement coverage indicates that 80% of the lines of code have been run through during the testing process. This metric helps in identifying parts of the code that have not been tested and may contain undetected defects.
It's important to note that achieving high statement coverage does not necessarily guarantee that all possible paths or scenarios within the code are tested, nor does it ensure the detection of all types of defects. Other coverage metrics, such as branch coverage or condition coverage, might also be necessary to achieve a more thorough testing process.
References:
* The official ISTQB CTFL syllabus clearly defines statement coverage and explains that it ensures that the corresponding percentage of all executable statements have been tested.