What is a stub and driver in integration testing

Improve Article. Save Article. Like Article. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. Therefore, these pseudo modules or stubs and drivers are mainly used for following reasons:.

Yes, basically the features and purpose of stubs and drivers are same. Both of them work as a substitute for the missing or unavailable module. However, the difference between them can be visualized during the integration testing. Therefore, to signify their differences, here is a comparison of stubs and drivers. The process of software testing cannot be completed with incomplete components and modules. Therefore, to ensure the accuracy as well as effectiveness of testing it is vital to create stubs and drivers that fulfil the requirements of incomplete or undeveloped modules and act as pseudo modules or codes that are called in for testing the functionality of major modules.

In short, there is no doubt that stubs and drivers are an integral part of software testing process. We deliver. Get the best of Professional QA in your inbox. Toggle navigation. Home Contact Us About Us. What is meant by Stubs and Drivers? Feb 12, Give your feedback! Get New Content Update.

Popular Posts. Data Flow Testing. Content Testing. Top Down Integration Testing is a method in which integration testing takes place from top to bottom following the control flow of software system.

The higher level modules are tested first and then lower level modules are tested and integrated in order to check the software functionality. Stubs are used for testing if some modules are not ready. 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. It makes use of both stubs as well as drivers.

The Integration test procedure irrespective of the Software testing strategies discussed above :. Skip to content. What is Integration Testing?

Big Bang Testing Big Bang Testing is an Integration testing approach in which all the components or modules are integrated together at once and then tested as a unit. Incremental Testing In the Incremental Testing approach, testing is done by integrating two or more modules that are logically related to each other and then tested for proper functioning of the application.

Stubs and Drivers Stubs and Drivers are the dummy programs in Integration testing used to facilitate the software testing activity. Bottom-up Integration Testing Bottom-up Integration Testing is a strategy in which the lower level modules are tested first. Top-down Integration Testing Top Down Integration Testing is a method in which integration testing takes place from top to bottom following the control flow of software system.

Sandwich Testing 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.