Wht is the Test Driver used in Integration Testing. Anybody
can expalin in Detail. Thanks in advance.
Answers were Sorted based on User's Feedback
Answer / ks thangavel
test driver is a dummy program which is used to replace the
lower level module in bottom-up testing
it is a calling component
BY
KS THANGAVEL
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / vivek.gupta
No my friend Ks Thangavel you are wrong here! please take
atmost care while answering question, coz here life is
concerned....
Test Driver: in bottom up approach, small modules r
developed,to test them a dummy core module called driver is
developed. so it is a dummy program which is used to replace
the core module in bottom-up testing.
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / anuradha
drivers and stubs are used when not all the modules are
ready during the integration
Is This Answer Correct ? | 3 Yes | 1 No |
Answer / cv
Answer by Mr.KS THANGAVEL is 100% correct.
Drivers are also known as "Calling" functions.
The reason being that the drivers are the dummy
functions which are used to test the core modules.
And To test the core module, we require to call the
function of core module which is only possible
by making a dummy calling sub-module which
is know as "Driver".
Whereas, Stubs are also known as called modules.
In Top-down approach we require to test the
correct functionality of all the sub-modules.
In this case we call the dummy modules which are
know as STUBS through core module.hence Stubs are
also known as "Called" functions.
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / madhusudhan
in bottom up approach programmers are interconnecting sub-programms without coming from main program.
main
|
DRIVER
|
sub1
|
sub2
driver is temporary program instead of main, driver activates the connection.
example : in login process, mailing and logout are constructed but login is under contstruction. so they use drivers to login and test.
in Hybrid approach also we use DRIVER.
STUB: is used in top-down approach, while interconnecting the main program and sub programs, in place of remaining which are un-developed programmers use stubs.
main
/ \
sub-b1 stub
| |
sub-b2 sub-a1
here stub stops the process, to sub-programms a1.
thanks for spending
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / kirti palshetkar
driver comes under integration testing.
in bottom-up approach tester go through lower level to upper
level modules.
once all lower modules get checked, tester need to test
upper modules (integrated all lower module)which is basically
call lower level modules as per req.. if this upper module
yet not developed by developer, tester need to take temporary
module which perform actual task of upper module.
this temporary module/ program is called as driver. which
main function is to call functions in lower level modules
hence is also called as' calling modules'
Is This Answer Correct ? | 0 Yes | 0 No |
what is status of defect when you are performing regression testing.
Is v-model cost effective when compared with all other models? If not which model is cost effective(low cost)?
As a tester how we resolve defect leakage? And how it occures?
What is the difference between Game (video game, mobile game, facebook game...etc) Testing and Software Testing? Why some company dont use testcase for Game, they only find bug and describe it directly to bugbase? And some testcase for Game if u think testcase is necessary for game (ex: testcase for Tetris game)
What is Equivalence partitioning,Boundary value analysis,Decision table testing,State transition testing,Use case testing. Plz explain with example and differences if any
How do we decide scope for smoke and sanity testing?
I have 2+ experience in manual testing but I can not use any bug tracking tool. I use excel sheet & mail that sheet to developer now I wan to change company is there any effect.
what is the difference between bug and issue?
Principles of testing?
Explain unit testing, integration tests, system testing and acceptance testing?
how can client know that the bug which has been corrected
Usecases and nounlists are associated with the following Requirement analysis methodologies 1.Information engineering 2.Object oriented analysis 3.Structural analysis 4.Functional analysis.