What is the Driver in Integration Testing..Anybody can
explain it.....Thanks in advance.....
Answers were Sorted based on User's Feedback
Answer / ramesh naik
In Bottom Up approach, the Child modules are developed
first. As the parent modules are developed, they are
integrated with the Child modules to perform integration
testing. In the process, if at all any parent module is
missing, inorder to continue the integration process, a
temporary program (called as DRIVER) is submitted in the
place of parent module.
| Is This Answer Correct ? | 7 Yes | 0 No |
Hi,
Basically integration testing can done in two ways
Top-down approach and Bottom up approach.
in top down approach we can use stubs.
in bottom up approach we can use drivers for integrating
the modules.using drivers for each new module being tested
in integration with all lower-level modules.
eg: we need to integrate 3 A,B,C modules then by using this
approach the lowest-level modules "B" and "C" are tested
with drivers. Next, the higher-level module "A" is tested
with a driver in integration with modules "B" and "C."
Finally, integration could continue until the top-level
module of the program is tested (with real input data) in
integration with the entire program.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / sreekanthreddy
drivers are simple program designed specifically for
testing that make calls to these lower layers......
| Is This Answer Correct ? | 1 Yes | 0 No |
Factors effecting Testing of Web Applications?
what is seviority and priority, and who will assign seviority and priority and High seviority and high priority , High seviority and Low priority and Low seviority and High priority and Low seviority and Low priority-- pls, if you know really give the answer,because in every interview they are asking plssssssss
8 Answers Deloitte, QuinStreet,
It will be a great help if any one will help on this issue, Three test cases got faied [TC#1, 2 and 3] and all are there in the same TestScript. For all the three failed testcases a bug is logged refrencing to the three failed testcase. In Next round of validation out of three two TC#2 and 3 got PASSED and TC#1 FAILED. I am confusssed if in this scenario if i mark the PASSED test case as PASS OR FAIl, as the the Defect will have BOTH PASS and FAIl at the same time. Please clarify How to handel this scenario.
Give an example of high severity and low priority bug?
why do u go for whitebox testing,when black box testing is available?
Describe me to the basic elements you put in a defect report?
any one please send me any test case examples with tabular columns in manual testing
what are different reports prepared by a tester and their templates.
What is difference between Sanity Testing & smoke Testing?
Explain a bug which if you have missed could have created a big problem?
Test approach to windows scheduler?
can someone give me a brief idea about embedded testing.. i know both embedded system concepts and testing concepts.. i just want to know what we have to do for embedded testing