The impossibility of complete testing has several significant consequences:

It means that we can never be completely sure that the software is free of bugs (A).

Without a definite stopping point, it becomes easier for some managers to justify minimal testing

efforts (B).

Since every testing task requires time and resources, it becomes challenging to determine which

tasks are always necessary (C).

These points highlight the need for a balanced and risk-based approach to testing, where priorities

are set based on the context and criticality of the software being tested​​.

Designing the tests is part of the Test Analysis and Design phase, not the Test Implementation and

Execution phase. The Test Implementation and Execution phase involves creating test suites,

executing test cases, and comparing actual results with expected outcomes to identify any

discrepancies​​.

Non-functional system testing evaluates various quality attributes of a system rather than specific

behaviors or functionalities. According to the ISTQB CTFL Syllabus, version 4.0, non-functional testing

encompasses several critical aspects:

Performance testing evaluates how the system performs under different conditions, such as load and

stress, to ensure it meets performance requirements.

Usability testing assesses the user-friendliness and overall user experience of the system, ensuring

that it is intuitive and accessible for end-users.

The syllabus outlines that non-functional system testing includes testing the quality attributes of the

system, which goes beyond just functionality and delves into performance, usability, reliability, and

other key attributes​​.

Statement coverage measures the percentage of executable statements in the code that have been

executed. However, it does not check for missing statements since these are not present in the code

to be executed in the first place. Statement coverage can identify unused branches, dead code, and

unused statements within the code. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.2​​.

Reviewing the test basis is a key activity in the Test Analysis and Design phase. This phase involves

analyzing the test basis documents (such as requirements, design specifications, and use cases) to

identify test conditions and design test cases. The ISTQB CTFL Syllabus explains that thorough review

of the test basis ensures that the tests are aligned with the specified requirements and design,

improving the accuracy and relevance of the tests​​.

Static analysis tools are used to detect certain types of defects without executing the code. According

to the ISTQB CTFL syllabus v4.0, typical defects found by static analysis tools include variables that

are never used, security vulnerabilities, and unreachable code. Poor performance and business

processes not followed are not typically identified by static analysis tools​​.

The fundamental test process consists of the following broad chronological steps:

Planning and control

Analysis and design

Implementation and execution

Evaluating exit criteria and reporting

Test closure activities

Option B correctly places three of these steps in the correct order: Analysis and design, followed by

Evaluating exit criteria and reporting, and finally Test closure activities. This order reflects the logical

sequence of performing detailed test analysis and design before executing tests and then evaluating

the results to determine if exit criteria have been met, followed by wrapping up the testing activities.

Reference: ISTQB CTFL Syllabus V4.0 - Section 1.4, The Test Process

The purpose of test completion criteria in a test plan is to define when to stop testing. These criteria

are used to determine if sufficient testing has been conducted to meet the test objectives and to

decide whether the product is ready for release. They typically include coverage goals, risk levels,

defect rates, and other quality indicators. According to the ISTQB CTFL Syllabus, defining test

completion criteria helps ensure that testing is both thorough and efficient, avoiding unnecessary

testing while ensuring the product meets quality standards​​.

The cost of fixing a fault increases as the software progresses through the development lifecycle.

Fixing defects identified early in the requirements or design phases is less expensive compared to

fixing those found later in testing or after the software has been deployed. This is due to the larger

impact on the system, more extensive rework required, and potential disruptions to the user

experience in later stages.

Reference: ISTQB CTFL Syllabus V4.0 - Section 1.2.1, The Cost of Defects

Testing should be stopped based on risk criteria defined for the system being tested. The ISTQB CTFL

syllabus v4.0 outlines that the decision to stop testing is influenced by risk levels, coverage achieved,

time and budget constraints, and the criticality of the system under test. Stopping criteria should

ensure that the risk of remaining defects is acceptable for the project stakeholders​​.