The basic idea of structure-based testing techniques is that the more details of the source code are executed, the more faults can be found. Structure-based testing techniques, also known as white-box testing or code-based testing, are based on analyzing the internal structure and logic of the software code. Structure-based testing techniques aim to achieve a certain level of coverage of the code elements, such as statements, branches, paths, conditions, etc. explains this as follows:
Structure-based testing techniques (also known as white-box testing techniques or code-based testing techniques) use the information of the internal structure of the component or system to derive test cases. They are commonly used at component testing and component integration testing levels, but can also be used at system and acceptance levels.
The main advantage of structure-based testing techniques is that they can reveal defects that are not easily found by other techniques, such as logic errors, incorrect assumptions, or incomplete paths. The main disadvantage of structure-based testing techniques is that they require access to the source code, which may not be available or feasible in some situations.
A, B, and D are incorrect statements about structure-based testing techniques. Structure-based testing techniques do not allow developers to have their own testing technique (A), as they follow predefined rules and criteria for coverage and test case design. Structure-based testing techniques do not do better testing, since the specifications are not needed (B), as they complement rather than replace specification-based testing techniques, which are based on the requirements and functionality of the software. Structure-based testing techniques do not gain time, since they are easier to implement than specification-based techniques (D), as they may require more effort and tools to analyze and execute the code.
