|
Author
|
Topic: Integration Test with Test Drivers
|
iroy
Member
Posts: 7
Registered: Jun 2001
|
posted 09-04-2001 11:11 PM
    
I am looking for some information on testing with drivers. You may count my knowledge on this as nil. I would like to know how Bottom-up integration test is performed using test drivers. How they are created and used to perform such tests. Also, if you could send me similar information regarding Top-down testing using stubs would be very useful. Thanks!------------------
|
creace
unregistered
|
posted 09-05-2001 06:53 AM
I'll try a rather simplistic example here.Let's say our system includes a module (or component or unit) which calculates square roots. I could write a test driver which would call this module via its specified interface and then display the results returned by the module. This test driver would allow the module to be called with a range of values to fully exercise the specified limits as well as any error checking (e.g. ask for square root of a negative number or of a non-numeric value). On the other hand, if the square root module hasn't been written yet, but I want to test a module which calls it, I could write a stub for the square root module which does nothing except return a '1' no matter what value I send it. This would allow me to continue testing the calling module although the actual results may be functionally invalid. All the stub needs to do is to declare its interface and generate any return values required by that interface. ------------------
Charles Reace Software Testing (n): 1. The art of trying to increase your confidence in a piece of software by finding everything that is wrong with it.
|
iroy
Member
Posts: 7
Registered: Jun 2001
|
posted 09-10-2001 12:53 AM
Thanks Charles...your explanation suffices an answer to my basic query. But does creating drivers mean that I am focussing more towards testing module functionality and performance than system integrity. And another theoritical query on this that's just being a bit inquisitive...how the names bottom-up and top-down?????? Also cud u let me know ways to create codes for both stubs and drivers? Does it require good development skills? If there is some material for reference do suggets same. Thanks once again!------------------
|
Charles Reace
Advanced Guru
Posts: 1299
Registered: May 2001
|
posted 09-11-2001 06:46 AM
I believe (I won't claim to be an expert in this area) that my description of using test drivers would pertain to "bottom up" development, while stubs are more for "top down". "Bottom up" implies you are creating the individual building blocks and testing them separately before integrating them, while "top down" has you coding the main "driver" programs first, then creating the lower level building blocks which the top blocks call, thus the need for stubs when first testing those top blocks.For a better explanation (as I certainly can't claim to be an expert on this), I'd suggest searching for a good software engineering book - maybe someone here can suggest such? ------------------
Charles Reace charles{DOT}reace{AT}verizon{DOT}net
|
iroy
Member
Posts: 7
Registered: Jun 2001
|
posted 09-11-2001 10:27 PM
Hi Charles! nobody else seems to be interested in this topic. Anyways, it's fine as I have got all my queries satisfactorily answered by you. so for me you are a guru, a preacher and a preacher is definitely an expert in the area! agreed!!
------------------
|
Charles Reace
Advanced Guru
Posts: 1299
Registered: May 2001
|
posted 09-12-2001 10:54 AM
Aw, shucks, you're making me blush. Anyway, glad to be of any help; and it's nice to get some positive feedback during these depressing days. Good luck.Charles ------------------
Charles Reace charles{DOT}reace{AT}verizon{DOT}net
|
iroy
Member
Posts: 7
Registered: Jun 2001
|
posted 09-13-2001 05:08 AM
I don't have words to express my shock and utter despair at the recent happenings. Although staying so far off we can imagine what people there are going thru.
However, if u r still in a mind to reply please let me know as to how to create stubs and drivers and the skillset required. Does Winnrunner/Robot support it? We r here to start off with Integration test v soon(right now manually). But r not v clear about the methodology to follow.------------------
|
Charles Reace
Advanced Guru
Posts: 1299
Registered: May 2001
|
posted 09-13-2001 07:22 AM
Stubs are normally written in the language that the actual program they are stubbing will be written in. In fact, ideally the stubs are created such as they can form the framework upon which the actual program is written. (You've already defined the interface, so now you just need to fill in the 'guts' of the program.)Drivers have more leeway, but they still need to be done in a language that can interface with the code they are to test. Naturally, writing them in the same language as the program to be tested will work, but I've also known programmers to write drivers in Visual Basic for testing C++ programs. I don't see any way to use a GUI test tool such as WinRunner for stubbing, and I doubt it would be practical to use it as a test driver, though you could possibly use it to add some levels of automation to a Visual Basic driver by using WR's data-driven testing features (this is hypothetical, I've not seen it done anywhere). ------------------
Charles Reace charles{DOT}reace{AT}verizon{DOT}net
|
annemarie
unregistered
|
posted 09-13-2001 07:49 AM
You might also check with your development team - in most of the environments I've worked in, they created Stubs a lot of times themselves for unit testing, and it might be that you could build off of those or at least use them as a reference point.------------------
Annemarie "What, exactly, do you mean by Change Control?" From "Top 10 Stupid Comments from Developers"
|
