It is passive; it waits to be called and returns hardcoded or predefined data. Example Scenario:
A "Login" module that needs to verify credentials against a "Database" module. The Problem: The Database module isn't finished yet. Examples Of Stubs And Drivers In Software 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) It is passive; it waits to be called
In software testing, and drivers are "mock" components used as temporary replacements for modules that are not yet developed or available. They are essential for incremental integration testing , allowing you to test specific parts of a system in isolation. 1. Stubs (The "Called" Program) Create a Stub for the Database
A driver is a temporary piece of code that simulates a . It "drives" the module under test by providing inputs and initiating execution. Difference between Stubs and Drivers - GeeksforGeeks