Test Stubs And Drivers For Mac

It is always a good idea to develop and test software in 'pieces'. But, it may seem impossible because it is hard to imagine how you can test one 'piece' if the other 'pieces' that it uses have not yet been developed (and vice versa). To solve this kind of difficult problems we use stubs and drivers.
In white-box testing, we must run the code with predetermined input and check to make sure that the code produces predetermined outputs. Often testers write stubs and drivers for white-box testing.
Driver for Testing:
Driver is a the piece of code that passes test cases to another piece of code. Test Harness or a test driver is supporting code and data used to provide an environment for testing part of a system in isolation. It can be called as as a software module which is used to invoke a module under test and provide test inputs, control and, monitor execution, and report test results or most simplistically a line of code that calls a method and passes that method a value.
For example, if you wanted to move a fighter on the game, the driver code would be
moveFighter(Fighter, LocationX, LocationY);
This driver code would likely be called from the main method. A white-box test case would execute this driver line of code and check 'fighter.getPosition()' to make sure the player is now on the expected cell on the board.
Stubs for Testing:
A Stub is a dummy procedure, module or unit that stands in for an unfinished portion of a system.
Four basic types of Stubs for Top-Down Testing are:
1 Display a trace message
2 Display parameter value(s)
3 Return a value from a table
4 Return table value selected by parameter
A stub is a computer program which is used as a substitute for the body of a software module that is or will be defined elsewhere or a dummy component or object used to simulate the behavior of a real component until that component has been developed.
Ultimately, the dummy method would be completed with the proper program logic. However, developing the stub allows the programmer to call a method in the code being developed, even if the method does not yet have the desired behavior.
Stubs and drivers are often viewed as throwaway code. However, they do not have to be thrown away: Stubs can be 'filled in' to form the actual method. Drivers can become automated test cases.

While doing an Integration , If we don't have all the modules get ready and Need to test a particular module which is ready then We Use Stubs and Drivers.
Stubs and drivers used in Integration testing for a Top Down Integration testing and Bottom Up Integration Testing.
For EX : If we have Modules x,y,z . X module is ready and Need to Test it , But it calls functions from y and z.(Which is not ready)To test at a particular module we write a Small Dummy piece a code which Simulates Y and Z Which will return values for X, These piece of Dummy code is Called Stubs in a Top Down Integration.
So Stubs are called Functions in Top Down Integration.
Similar to the above ex: If we have Y and Z modules get ready and x module is not ready, and we need to test y and z modules Which return values from X,So to get the values from X We write a Small Piece of Dummy code for x which returns values for Y and Z,So these piece of code is called Drivers in Bottom Up Integration
So Drivers are calling Functions in Bottom Up Integration.
Thanks
Sandeep