Interested to Buy Any Domain ? << Click Here >> for more details...
What is stub and driver in integration testing ?
Explain with example.
- 11 Answers
- 81680 Views
- Accenture, Taleem India, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / sangeetha
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)
wat the testers wil do thy wil place dummy modules and
integerate these dummy modules with the higher level
modules.in top down apparoach the dummy modules r called
Stubs.
Stubs- Def
stubs r the dummy modules tht simulates the low
level modules.
Bottom up:
in this the dummy modules r called drivers.
Drivers- Def:
drivers r the dummy modules tht simulate the high
level modules.
| Is This Answer Correct ? | 239 Yes | 22 No |
Answer / mfsi_chinmayb`
Hi
Let me give a brief idea about Integration testing.
As the name suggest it is a process to sum up or assemble
different modules of the project and then jump for a testing
Let's we have three modules A,B,C.
While integration testing we have complete module A
developed but the rest are in construction.If we need any
function from B or C then we need to create a dummy one for
that t make the testing success for A.
Here the STUB is the dummy function for B or C and the
DRIVER is the module A who called the stub.
In the bottom to up approach(B,C are ready and A is undone)
then the DRIVER is B or C and the STUB is Dummy function.
| Is This Answer Correct ? | 19 Yes | 8 No |
Answer / joy
stubs - we can say use of dummy module to test the main functionality.for eg to test the application for billing payment while the connection to the sever is not ready then we can use stubs to test the billing application.
Driver :- same as above in this we test the sub module when the main part is not developed.for eg:-login page where login functionality is not developed while u can test the remiaining part
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / sreedevi
Test Drivers are used during Bottom-up integration testing in order to simulate the behaviour of the upper level modules that are not yet integrated. Test Drivers are the modules that act as temporary replacement for a calling module and give the same output as that of the actual product.
Drivers are also used when the software needs to interact with an external system and are usually complex than stubs.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / kunal
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)
wat the testers wil do thy wil place dummy modules and
integerate these dummy modules with the higher level
modules.in top down apparoach the dummy modules r called
Stubs.
Stubs- Def
stubs r the dummy modules tht simulates the low
level modules.
Bottom up:
in this the dummy modules r called drivers.
Drivers- Def:
drivers r the dummy modules tht simulate the high
OR
Integration testing: carrying out integration tests.
Integration tests (After Leung and White) for procedural
languages. This is easily generalized for OO languages by
using the equivalent constructs for message passing. In
the following, the word "call" is to be understood in the
most general sense of a data flow and is not restricted to
just formal subroutine calls and returns ? for example,
passage of data through global data structures and/or the
use of pointers.
Let A and B be two components in which A calls B.
Let Ta be the component level tests of A
Let Tb be the component level tests of B
Tab The tests in A's suite that cause A to call B.
Tbsa The tests in B's suite for which it is possible
to sensitize A -- the inputs
are to A, not B.
Tbsa + Tab == the integration test suite (+ = union).
| Is This Answer Correct ? | 13 Yes | 15 No |
Answer / manjunath
Consider that module A is ready to test and module B is not yet ready. in order to test module A we need another module for this purpose we create a dummy module B called stub
defnation of stub- stub is a dummy module which recives data where as actual module recives data and sends respones to moduke B
Driver-we need somthind to recive data and send response this is called driver
| Is This Answer Correct ? | 5 Yes | 9 No |
Answer / k.manasa
integration testing means integrate the modules and then do
testing
3 phases of integration testing
top-down
botttom-up
sand-witch
top-down:
in top-down approach top module is coded one and
the remaing modules below the top is not coded ones.
here the top module is treated as driver and bottom modules
treated as stub.
Driver:Driver is a set of functions which is driven by
another set of functions.
Stub:A stub is set of functions driven by the driver.
these sub modules are also coded by developer at the time
of developing,but these are the temperory ones.
| Is This Answer Correct ? | 9 Yes | 20 No |
Answer / raja
Integration testing: carrying out integration tests.
Integration tests (After Leung and White) for procedural
languages. This is easily generalized for OO languages by
using the equivalent constructs for message passing. In
the following, the word "call" is to be understood in the
most general sense of a data flow and is not restricted to
just formal subroutine calls and returns ? for example,
passage of data through global data structures and/or the
use of pointers.
Let A and B be two components in which A calls B.
Let Ta be the component level tests of A
Let Tb be the component level tests of B
Tab The tests in A's suite that cause A to call B.
Tbsa The tests in B's suite for which it is possible
to sensitize A -- the inputs
are to A, not B.
Tbsa + Tab == the integration test suite (+ = union).
| Is This Answer Correct ? | 22 Yes | 55 No |
Answer / vaidehi
plz look at book...............
plz preffer self study not internet
| Is This Answer Correct ? | 11 Yes | 55 No |
What is GreenBox Testing
Dear friends, I am Ravi, was working as a Test Manager and quit the job due to some personal reasons. I need to get into job at any cost, as it is very critical situation for me. Now I am preparing for interviews, and I seed your help. Please mail me at globalpease2008@gmail.com I'll definitely share all those topics in this form too.... Expect your help and thanks in advance. Regards, Ravi
explain current project?
what is testing phase??
Is v-model cost effective when compared with all other models? If not which model is cost effective(low cost)?
Tell me your views in this project?
what is Scalability,Critical Analysis
I m 2009 pass out B.E. student and still searching job.last 3-4 interviewer asked me why r u not selected any company till now...but i didn't give properly answer so any one can tell what should i have to say abt this which will give positive impression to interviewer.
what is the diffrence b/w verification and validation?
HOW DO U WRITE DEFECT REPORTS? WHAT IS FORMAT IN GENERAL WAY
How will confirm the Test Cases are passed?
I have tested ecommerce site, but when i search for any product Or access any page, some time i found it missed the values from my URL..EXAMPLE : we take this URL "http://www.allinterview.com/forms/questionform.php" This is the actual URL & it is ok but when i test it displays like "http://www.allinterview.com//questionform.php" NOTE : In above URL "forums" is missing.. I dont know why this happens as i have checked all the code & tested again & again but it dont know the reason. HELP ME plz... Thank you
Automation Testing 
