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

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.

Answer / anuradha

drivers and stubs are used when not all the modules are
ready during the integration

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.

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

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'

In testing can you explain the concept of work bench?

1 Answers  

How many scripts u use to run daily?

1 Answers   HCL,

today evening you need to release software to client.at that time you found a defect.How you convence him?

0 Answers   RealPage,

What is the quality process is following in your organization.

0 Answers  

Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams.

1 Answers  

How Defect prevention can be accomplished ?

2 Answers   Crea,

Differentiate between severity and priority? who assign these parameters to a bug?

6 Answers   Satyam,

What different impact rating’s you have used in your project?

0 Answers  

what are the examples for web based applications and Client Server Applications

5 Answers   ASD Lab, CFCI, College School Exams Tests, GXS,

1]Give me Two examples for - High Priority and Low Severity?? 2]Give me Two Examples for - High Severity and Low Priority??

2 Answers   SunGard,

What is Automation Test frame work ?

1 Answers   Virtusa,

What is the exact diff between sanity and smoke test and who will do in real time?

3 Answers