home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!convex!convex!ssimmons
- From: ssimmons@convex.com (Steve Simmons)
- Subject: >>> Value of High Code Coverage Metrics in Testing - Request for Opinion
- Sender: usenet@news.eng.convex.com (news access account)
- Message-ID: <ssimmons.724336081@convex.convex.com>
- Date: Mon, 14 Dec 1992 12:28:01 GMT
- Nntp-Posting-Host: pixel.convex.com
- Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
- X-Disclaimer: This message was written by a user at CONVEX Computer
- Corp. The opinions expressed are those of the user and
- not necessarily those of CONVEX.
- Lines: 27
-
-
- Performing test coverage analysis on code is more of a good attitude than
- it is a silver bullet for removing bugs. There is an old mgmt saying,
- "What is inspected is what gets done".
-
- > 1) Do people think that this is a valuable metric?
-
- Again, it improves the code but it does not remove all bugs. Design flaws
- about cases not being handled cannot be found. Also, any code that uses data
- driven tables (e.g. finite state parsers) cannot be measured effectively.
-
- > 2) Is it a cost effective excersize to get engineers to achieve a particular
- > %BFA as a completion criteria?
-
- Sure... if you have the time in the schedule and effective tools to do it.
- Usually, it is best to have people do coverage analysis on their own code
- and have people who don't know the code test it for unanticipated conditions.
-
- > 3) What is a realistic %BFA to aim for?
-
- Fairly low percentage of 50% is usually the maximum possible value. Much
- code is assertion testing. However, every condition should be accounted.
-
- Thank you.
-
-
- Steve Simmons
-