Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!stc!rmj
From: rmj@tcom.stc.co.uk (Rhodri James)
Newsgroups: comp.lang.c
Subject: Re: Determining C Complexity
Keywords: metrics
Message-ID: <1805@jura.tcom.stc.co.uk>
Date: 6 Aug 90 16:58:48 GMT
References: <3205@mica6.UUCP> <1050@ashton.UUCP> <142@srchtec.UUCP> <2592@dataio.Data-IO.COM> <1990Jul26.165322.2729@zoo.toronto.edu> <140003@sun.Eng.Sun.COM>
Reply-To: rmj@htc2.UUCP (Rhodri James)
Organization: STC Telecomms, Harlow Technical Centre, Harlow
Lines: 10

To give an example of a metric which certainly is useful, how about the
percentage of code actually tested? This was very revealing when it was
first introduced in various companies -- at one that I know, the
engineers discovered that their initial testing covered less than 10% of
the code, and "really thorough testing" tended to get about 60%
-- 
* Windsinger                 * "Nothing is forgotten..."
* rmj@islay.tcom.stc.co.uk   *                    Mike Whitaker
*     or                     * "...except sometimes the words"
* ...!mcvax!ukc!stc!rmj      *                    Phil Allcock