Final answer:
Whitebox testing involves a thorough examination of the code's internal structure, including code walkthroughs, static analysis at compile time, and examination of a subsystem's implementation details. Options A and D describe whitebox testing, while option B can be part of it; option C aligns with blackbox testing techniques.
Step-by-step explanation:
Whitebox testing methodology indeed involves looking at the internal structure of the code. It includes different techniques:
- Code walkthrough, which is a systematic, line-by-line review of the code.
- Static analysis of code at compile time, which examines the code without actually executing it.
- Providing inputs to the application and validating that the actual output matches the expected output (this is more commonly associated with blackbox testing).
- Examining the implementation details of the subsystem of an application, which requires knowledge of the internal workings.
Therefore, options A and D are directly related to whitebox testing, as they involve a deep dive into the code structure and logic. Option B can be a part of whitebox testing, whereas option C is more relevant to blackbox testing.