Interested to Buy Any Domain ? << Click Here >> for more details...
What is stub and driver in integration testing ?
Explain with example.
- 11 Answers
- 80773 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 non functional requirements used in ur project?
what is water fall model?
What r all the security problems u r facing & the measures taken to solve.
What is difference between Defect and Bug?
What scripting language should tester know when his organisation using Automation tool like wise any tool? wht kind of script should tester should be familiar?
what is fpa ?
diff between water fall model and v-model?
Can anyone explain me these 3 techniques with an example? 1).Equalent Class Partision 2).Cause-Effect Graph analysis 3).Error Guessing.
what r the fields present in requirement tracability metrice (RTM)?please explain each and every field as i m not aware.
Could you please give me an example of test scenarios for online banking testing (like billing,payment,statements etc.) (like how to test the functionalities of Payment module, Billing module...etc.)?
how to intaract with clint? which purpose? plz tel me
why do you go for white box testing when black box testing is available?
Automation Testing 
