Statement testing is a structure-based (white-box) technique. This technique involves testing the internal structure of the application, focusing on the execution of the statements within the code. The goal is to ensure that every statement in the code has been executed at least once during the testing process. Other options like decision table testing, state transition testing, and boundary value analysis are black-box techniques, which do not require knowledge of the internal code structure. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.1.

Walkthroughs are often led by the author of the document and are used to aid learning and understanding among team members. These informal review meetings help in discussing the content and obtaining feedback from participants, but they are less formal than inspections and do not necessarily involve defined roles for all participants or result in documented outcomes. Reference: ISTQB CTFL Syllabus V4.0, Section 3.2.1.

Component testing focuses on the individual parts of the software, often using design specifications, component specifications, or data models to derive test cases. In contrast, system testing evaluates the entire system's functionality and performance, using requirements and functional specifications or usecases to develop test cases. The ISTQB CTFL Syllabus clarifies these distinctions, emphasizing the different sources for test case derivation and the scopes of each testing level.

A data-driven approach to test automation design involves separating the test data inputs from the test scripts.
This approach allows the same generic script to read different sets of test data and execute the same test steps with various inputs. This method enhances reusability and efficiency in automated testing by allowing testers to run multiple test scenarios using the same script but different data sets.