Did u come across STUBS and DRIVERS?How did u use these in
u r project ?
Answers were Sorted based on User's Feedback
Answer / jyothinapa
Stubs and Driver comes under integration testing.
integration testing means integrating the modules and
perform testing on that.
integration testing can be performed in 3 approaches
1.Top-Down approach
2.Bottom-Up approach
3.Hybrid approach
Top-Down approach means integrating the main module with
the sub module.during this time if some of the sub modules
are not finished that is if they are in
underconstruction,to continue the integration testing we
will put one stub in the place of constructive sub module.
In bottom-up approach the integration is performed from
bottom to up.here sub modules are integrated with main
module.during this time if main program is not ready that
time we will put driver instaead of main program for
continuing integration testing once they are fully
constructed the main program we aill replace that driver
with the main program.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / sailaja
these two are used in integration testing.
Stub; is used in Top down integration testing to simulate
the called module
Driver:is used in bottom up integration testing to simulate
the calling module
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / jyothi
At the time of integration development team finds one of
the sub module is yet to be released from unit testing then
they install a virtual environment is called 'stub'nd
continues integration testing based on main module in top
down manner
if main module is yet to be released from unit testing then
they continues integration testing in bottom up approach by
installing 'driver' in place of main module
| Is This Answer Correct ? | 3 Yes | 0 No |
i will give a gen example....suppose u have 3 modules...A B
C...A n B r 100% comp....and C is only 50% comp....u r under
pressure to comp in a time frame...what u do is u know to
build the mod C u need at least 15 days...so u build a dummy
mod C which wil take 1/2 days...This is STUB
now once all the mod A B and C(dummy) r ready..u integrate
them to see how it works..This is a DRIVER
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / dilip
Stubs and driver are dummy program written bt the
programmer when the real component are not reday for
testing.
Drivers are nothing but calling program and stubs are
called program.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / sekhar
hi jyothinapa thanq for giving answer
please explin abt hybrid approach also
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / shiva
STUB
While creating the module in to a top-down approach,if at all any mandatory module is missing then replace that module with temporary program tahat is called stub.
DRIVER
While creating the module in to a bottom-up approach if at all any mandatory module is missing then replace that module with temporary program tahat is called driver.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / aditya
Stub : A piece of code that simulates the activity of
missing components.
Driver : A piece of code that passes test cases to another
piece of code.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / sunithayagnamurthy.heartcom in
Hi Manam,
This is sunithayagnamurthy.stub and driver both
are included in integration testing.Integrate testing means
to test sub modules and modules.this is called integration
testing
integration testing is divided two types
1.top down approch
2.bottom up approch
top down approch: top down approch means to test the main
module to submodule.some times the main module is till not
developed temparary module is created .this tempatrary
module name called stub.It is act as main module
bottom up approach:bottomup approach to test the sub mdule
to main module some times thesub module is till not
developed the temparary module is created.this temparary
module name is calles driver.It is act as submodule....
If any mistakes is thr please excuse.....
send correct answer
| Is This Answer Correct ? | 0 Yes | 5 No |
What are the different test deliverables?
What are the different phases available in STLC.
Anyone attended the manual testing interview with L&T infotech in recent past. please let me know the type of questions they can ask especially in PM round. Thanks
Q.Reasons not to automate. a.No formal test plan. b.No Design document. c.Testing budget is minimal. d.All of the above.
How u test MS- Vista without any requirement Doc.
Does Automation replace Manual Testing?
what is the Slippage Ratio in your company?
Hi, Glamrous Should I write the test case for dropdown field For Above: -ve test case Test Case Name Expected Esult Without selecting Category - Default category should get select Is this a valid test case?
what is the difference betwen quality center version 9.0 and version 10.0
. Diff. between Application server and web server? 2. Default port number of Tomcat? 3. bug life cycle? 4. what is defered status in defect life cycle? 5. smoke test? 6. Do you use any automation tool for smoke testing?? 7. verification and validation? 8. Testing process in your comp.? 9. Testing methodology? 10.when a bug is found what is the 1st action? 11.what is best bug in your current proj. which you found?? 12.what is test plan and explain its contents? 13.Advantages of automation over mannual testing? 14.explain some SDLC models? 15.ADhoc testing? 16.what is mean by release notes? 17.what are all the contents of release checklist? 18.when a new build comes what is 1st action?(performing smoke test). 19.how many test cases will you write for 1 day? 20.what is the bugbase do you use in your comp.?
1)can u tell me, what is the roles and responsibles for database tester in DB testing from requirement stage to UAT stage....2) what are the i/p documents he wants and who wil give the i/p docs. to DB tester.and tell me what exactly db test case means what?
how would u ensure 100% coverage testing?