scott@vicorp.UUCP (Scott Reed) (11/28/89)
At the end of October I posted a request for information on tools
for testing and validating C software programs. Several people
requested that I post a summary of responses. Here it is.
***************************************************************
From: uunet!urbana.mcd.mot.com!marick (Brian Marick)
A company called Software Research Inc has coverage analyzers (branch
and path) and some regression test tools. I don't know much about
them. They're kind of pricey -- ~$6000 for branch coverage (price
depends on machine type).
Dan Exon 415-957-1441 SRA, testing tools
I've done a "proof of concept" prototype branch coverage tool with the
GNU C compiler. I estimate 14 days to produce one from it (including
documentation and testing, of course). I will begin working full time
on my PhD in January. Most likely, I'll need a branch tool for my
testing research, so I may take the time to write it. If I do, I'll
make it available for anonymous FTP.
Two other sources:
NTIS has some number of freely-available in-house tools.
Delores Wallace NTIS Testing person 301-975-3340
wallace@swe.icst.nbs.gov
Software Quality Engineering has a testing tools reference guide. It
costs $150. 1-800-423-TEST.
bem.
***************************************************************
From: uunet!uts.amdahl.com!lms (Linda Sorauf)
Most of the tools we use for testing C programs were developed
in-house and are not available outside. We have one program called
tcov which gives information about what lines of code and what
decisions were executed how many times by a given test case.
We have also found 'make' to be very valuable in setting up
regression test suites.
Linda
***************************************************************
From: System Administrator <uunet!iex!root%athens.iex.com>
I am sure you are aware of the McCabe (and similar) complexity metrics that
are available for C source files. Beyond that there are some improving
browsers available for commercial sale. I know of no commercially available
tools for testing itself (wait there are "capture" routines which allow later
playback of the commands given to a system which can be used for confirmational
testing, these are available on both unix and msdos.)
The McCabe tools allow the tester (and the author) to determine the more
complex pieces of code and spend time reviewing them in detail, under the
assumption that they contain the largest defect density.
An additional type of tool provides branch coverage analysis, that is normally
utilized for unit testing. This records the actual code executed within a
module.
Both the metric tools (McCabe, Halstead etc.) and the branch coverage analysis
tools are available for HP workstations directly from HP.
herb
***************************************************************
From: uunet!cs.utexas.edu!cg-atla.samsung.com!bradlee (Rob Bradlee)
First, I think a metrics program can be a big help. An inexpensive but
well done one is available from
SET Laboratories, inc
P.O Box 83627
Portland OR 97283
(503) 289-4758
They have versions for both PCs and Suns.
Second, if you want to spend the big bucks, Tom McCabe himself sells two
tools. ACT draws a control flow chart of each routine, and Battlemap
with reverse-engineer your C code and make a structure chart out of it.
However, I believe it cost $20k. If you decide your interested send
me mail and I'll find the address.
Hope these help. Oh by the way, if you haven't already done it, get
Glenford Myers' book "The art of Software Testing" from John Wiley & Sons.
Mccabe's address:
McCabe & Assoc.
Twin Knolls Professional Park
5501 Twin Knolls Road
Suite 111
Columbia, MD 21045
***************************************************************
Thanks to all who helped me on this.
If you would like to add to this summary, please do!
- scott
Email: scott@vicorp.uu.net
Scott Reed
V.I. Corporation
Amherst Research Park
Amherst, MA 01002 USA
(413) 253-3482