Re: Testing a program

Mani wrote:

> Thanks David. I checked the Silvon test monitor site.
>
> I am interested in hearing about real-life experiences of using similar test 
>coverage analyzer tools (Vendor or home grown). Further, I am also interested 
>to know if the outputs from these tools are being used to prepare/improve the 
>test data.
>

Although I never used it myself, there was an article about 10 years ago or so 
in a 3X/400 trade rag which had a program which took a source member, added an 
array, and inserted a counter after every op code. The array index was the 
source statement number.  The purpose was to let
you know in a given test run which statements were executed and how many times. 
 Not only would that let you know if you had deficient test data (statements 
not executed) but you could look at the high count lines to see if they could 
be restructured.

Could be a good start point for some home grown testing tool.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---