SOFTWARE TESTING
TEST PLAN AND TEST CASE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Bottom-up Integration Testing.
|
|
|
Sandwich Testing.
|
|
|
Top-down Integration Testing.
|
|
|
None of the above
|
Detailed explanation-1: -This method is also called “sandwich testing.” It involves simultaneously testing top-level modules with lower-level modules and integrating lower-level modules with top-level modules, and testing them as a system.
Detailed explanation-2: -Sandwich Testing is a strategy in which top level modules are tested with lower level modules at the same time lower modules are integrated with top modules and tested as a system. It is a combination of Top-down and Bottom-up approaches therefore it is called Hybrid Integration Testing.
Detailed explanation-3: -In the top-down approach, the stubs are used to simulate the submodule, which implies that the Stub works as a momentary replacement. On the other hand, in the bottom-up testing approach, the drivers simulate the main module, which means that the Driver works as a momentary replacement.
Detailed explanation-4: -Bottom-up testing: Bottom-up (also known as bottom-to-top) integration testing is the opposite of the top-down approach. It involves testing lower-level modules first, and then gradually progressing incrementally to higher-level modules. This approach is suitable when all units are available for testing.