Primarily used in Top-Down Integration Testing .
It is passive; it waits to be called and returns hardcoded or predefined data. Example Scenario: Examples Of Stubs And Drivers In Software Testing
A stub is a dummy module that simulates a . It is used when the main module is ready for testing, but the sub-modules it depends on are still being built. Primarily used in Top-Down Integration Testing
Create a Stub for the Database. When the Login module calls checkUser() , the Stub simply returns true (success) without actually searching a real database. This allows you to verify if the Login module correctly redirects the user to the dashboard. 2. Drivers (The "Calling" Program) Examples Of Stubs And Drivers In Software Testing
A "Login" module that needs to verify credentials against a "Database" module. The Problem: The Database module isn't finished yet.