What is stub and driver in integration testing ?
Explain with example.
- 11 Answers
- 77520 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 |
Just now i got a bug in the application.Anyone of u can clarify me is it a bug or not. scenario is: 1. if we a check box more than one. 2. click TAB and keep the focus on any check box not on the last check box 3. Then click (space+tab) at a time 4. then check the changes if we click anywhere the previous check box is going to be checked and the application is going to be hanged........... please answer to this question.If i have reported this to my developers they are telling that this is a browser property please confirm this scenario at ur developers and answer to me please .thanks in advance........ (glamorous)
What is a test scenario? write atleast 15 test scenarios for gmail?
Write 2 scenarios for Integration testing? Please let me know its urgent.
What is the difference between debugging and manual testing?
How to test the functionality & UI of an application which is in a different language other than English as part of Localization Testing.
What are the interview question on insurance domain in manual testing
Difference between manual testing and system testing
Difference between or when do you conduct Acceptance testing User Interface testing ?
What is test data
If you are handling a product testing and if there are around 100 test cases and in them few test cases are failed then at the end of the day how will you treat whether the product is pass/fail.? consider the failed test cases are in functional requirements.
8 What can static analysis NOT find? a) The use of a variable before it has been defined b) Unreachable (“dead”) code c) Whether the value stored in a variable is correct d) The re-definition of a variable before it has been used e) Array bound violations
password is having 6 digit alphanumerics then what r the possible input conditions?
6 Answers Logica CMG, Visual Soft,
Automation Testing 
