From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=3.0 tests=BAYES_00,TO_NO_BRKTS_PCNT
	autolearn=no autolearn_force=no version=3.4.5-pre1
Date: 18 May 93 14:47:46 GMT
From: news.crd.ge.com!e7sa!groleau@uunet.uu.net  (Wes Groleau X7574)
Subject: Re: Ada coverage tools?
Message-ID: <C7893M.3pu@crdnns.crd.ge.com>
List-Id: <comp.lang.ada>

In article <troj.737690596@cwis> troj@cwis.unomaha.edu (Kevin Trojanowski) writ
es:
>Anyon happen to know of, or better yet, have experience with coverage tools
>for Ada?  We are currently looking into acquiring a coverage tool to use
>on our current and future Ada projects.

If you mean a tool to document which logic paths have been executed, I suggest
investigating Logiscope from a company called Verilog.  I do NOT recommend 
AdaDL.  Logiscope's user interface is not particularly intuitive, but I have
OFTEN seen worse.  It also provides graphics of the structure of single units,
graphics of the interelationships (calling paths) of groups of units, metrics
such as those defined by Halstead, McCabe, Schott, and others, and various
reports on whether each unit is acceptable, rejected, or borderline (according
to formulae defined by the user in terms of the metrics).

Logiscope can also be used on C, FORTRAN, COBOL, Pascal, several assemblers,
and I think some others not listed in my manual to an old version.

We use it on a large project (over four million lines of code already
delivered and much more to go) which is about 90% Ada.  In addition to 
"required" usage, I have found it very helpful in helping me figure out
the structure of somebody else's sloppy code when I get the fun job of
fixing it!!

Wes Groleau