Software Quality Assurance Practice Exam

What is true about top-down testing?

1. It doesn't require any previously tested modules

2. The next module for testing must have tested subordinate modules

3. It can only be applied in small projects

4. It ensures only integration of modules

The correct answer is: The next module for testing must have tested subordinate modules

The statement that the next module for testing must have tested subordinate modules is true for top-down testing. This approach begins with testing the highest-level modules and progressively integrates lower-level modules that interact with them. In a top-down testing strategy, the top-level module is tested first while the subordinate modules can initially be stubbed, which means placeholders are used to simulate their functionality. Once the higher-level module works as expected, individual subordinate modules are gradually tested in tandem, ensuring that the entire system operates properly as a cohesive whole. This method is effective for identifying interface and interaction issues early in the development process, as the focus is on ensuring that higher-level functionality works as intended before delving into the details of each subordinate module. Employing this strategy allows testers to build confidence in the overall system architecture before concentrating on lower-level functionalities, thus enabling a smoother integration process as modules are added. In contrast, the other provided statements do not hold true when discussing top-down testing methods. It can accommodate projects of various sizes, and while it does focus on module integration, its primary purpose is not solely to ensure integration but also to validate the functionality of system components as they interact. Lastly, previously tested modules contribute to reducing risks during testing, rather than being a