Interested to Buy Any Domain ? << Click Here >> for more details...
What is the Difference between Stub Testing and Driver
Testing?
- 9 Answers
- 39283 Views
- CTS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / shalini
stub testing:
In top down approach,a core module is developed.to test
that core module, small dummy modules r used.so stubs r
small dummy modules that test the core module.
Driver testing:
in bottom up approach, small modules r developed.to test
them a dummy core module called driver is developed.
| Is This Answer Correct ? | 64 Yes | 10 No |
Answer / govind
These are the different types of integration techniques
Stub: When u approached top down approach you have to use
stubs. ie when testing the module from top level hierachy
to bottom level hierachy
DEF: Stub is nothing but a calling function for the
function to be tested.
Driver: When u approached bottom up approach you have to
use driver. ie when testing the module from bottom level
hierachy to the top level hierachy
Driver: Driver will act as a dummy program for the fucntion
to be tested
| Is This Answer Correct ? | 49 Yes | 6 No |
Answer / neelohit
# 1 types of integeration testing:
top down
bottom up
Top down :
testing hierarchy starts from higher level
to lower level.if suppose testers dnt get the lower modules
for testing(consider the lower modules are under developmnt)
what the testers will do they will place dummy modules and
integerate these dummy modules with the higher level
modules.in top down apparoach the dummy modules are called
Stubs.
Stubs- Define as --> stubs are the dummy modules tht
simulates the low level modules.
Bottom up: In this the dummy modules are called drivers.
Drivers- Def: Drivers are the dummy modules tht simulate
the high level modules.
| Is This Answer Correct ? | 13 Yes | 2 No |
Answer / yasir
Stub means a Dummy model of a particular module.
Suppose we have to test the interface between 2 modules A
and B and we have developed only module A while Module B is
yet in development stage.
So in such case we can not test module A but, if we prepare
a dummy module, having similar features like B then using
that we can test module A.
Our main aim in this is to test Module A & not Module B so
that we can save time otherwise we have to wait till the
module B is actually developed.
Hence this dummy module B is called as Stub.
Now module B cannot send/receive data from module A
directly/automatically so, in such case we have to transfer
data from one module to another module by some external
features. This external feature used is called Driver.
| Is This Answer Correct ? | 10 Yes | 0 No |
Answer / vishnukumar.
a temporary files when doing the integratin test.
developers use stubs and drivers for time being to conduct
the test.
after the original modules are developed these will be
replaced with the actual one.
for the base modules replacement they use drivers and
for the core modules replacement they use stubs.
| Is This Answer Correct ? | 11 Yes | 3 No |
Answer / raj
stub testing:
In top down approach,a core module is developed.to test
that core module, small dummy modules r used.so stubs r
small dummy modules that test the core module.
Driver testing:
in bottom up approach, small modules r developed.to test
them a dummy core module called driver is developed.
| Is This Answer Correct ? | 7 Yes | 1 No |
Answer / maddy
Driver: test tool that replaces a component that takes care
of the control or the calling of a component or system
Stub: special purpose implementation of a software
component that calls or is otherwise dependent on it . it
replaces a called component
| Is This Answer Correct ? | 8 Yes | 4 No |
Answer / aneesha
STUB:In top down integration testing stubs are used.lower
level modules are normally simulated by stubs,as u add
lower level code,u will replace stubs with the actual
components.
DRIVER:It is a sub module of main module.this is used in
bottom up integration.After completiong the testing.u will
replace the sub module.i.e drive
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / dharmaraj allukapally
TEST STUB:-
While integrating(combining) the modules in Top down approach,
if at all, any mandatory module is missing, then that module
is replaced with a temporary program known as TEST STUB
TEST DRIVER:-
While integrating the modules in bottom down approach,
if at all, any mandatory module is missing, then that module
is replaced with temporary module known as TEST DRIVER
dharmarajttestengr@gmail.com
9885531134
| Is This Answer Correct ? | 0 Yes | 6 No |
what is defect density?
What are all the scenario for 1.google analytics 2.api 3.paypal
What report u generate after completing testing?
Could anyone explain me how to write scenerio for login screen?
what do you understand by browser and what r the types?
When do you feel that testing should start now while developing an application.
Why position WinRunner and the AUT so they do not overlap?
Whats the difference between retesting and regression testing, explain SDLC and STLC, test plan, test case template, severity and priority, write test scenarios for login screen, and employee payroll; BVA and EP for a particular eg.
Please tell me some test cases for GOOGLE.COM
Are Test Condition and Test Description/Procedure are different? Please Reply
At what stage of the life cycle does testing begin?
as a tester, do u know only ur module requirements or other module req's also?
Automation Testing 
