Feature #10726
calculate and report code quality metrics
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#1 Updated by Greg Shah 9 months ago
We will implement multiple calculations of code quality using TRPL (and possibly a subset of call graph analysis). These are the top measures we should be looking to implement:
- Cyclomatic Complexity (see also the related Essential Complexity)
- Halstead Complexity Measures
- Lines of Code per File or Top Level Block Type (file/class, external procedures, internal procedures, functions...)
- Code Duplication (we may need some results from #9721 or #1730 / #1740 to help identify duplication)
- Counts for Application Resources (e.g. number of screens, or the number of different tables used within some sub-division of code)
Detection of matches to coding standards and "code smells" issues will overlap here with the work for linting (#3703). The metrics will be provided as reports and after #10700, will be directly surfaced in our IDE support.
I'm open to adding other measures, post your suggestions here.
#2 Updated by Greg Shah 9 months ago
- Related to Feature #3703: implement TRPL based linting support added
#3 Updated by Greg Shah 9 months ago
- Related to Feature #10700: expose analytics features in our IDE support added