This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 175722 - [68cat] Include a measure of complexity in code coverage report
Summary: [68cat] Include a measure of complexity in code coverage report
Status: NEW
Alias: None
Product: contrib
Classification: Unclassified
Component: Codecoverage (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Schovanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-29 22:52 UTC by dynamite
Modified: 2009-10-30 09:07 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dynamite 2009-10-29 22:52:43 UTC 
[ BUILD # : 200910281401 ]
[ JDK VERSION : 1.6.* ]

Classes that are of greatest need to high/complete code coverage are those that are the most complex.  The total number
of lines is a simple indication of complexity, but there are much better measures out there including cyclometric
complexity.  I seem to remember a module in the past that could give this very value.  It would be useful if this
measure could be incorporated into the code coverage report to make is easier to identify those classes that require
the greatest attention.