# Lines of Code in Types 100% Covered
A covered line is even more valuable in a type 100% covered. Covering 90% of a class is not enough: the 10% uncovered is hard-to-test, hence not well-designed, hence error-prone. Better test error-prone code, isn't it?
CQLinq source
This trend metric is written in CQLinq, C# LINQ over the NDepend code model. It ships with every new NDepend project: you can read it, adapt it, or use it as a starting point for your own custom rules.
// <TrendMetric Name="# Lines of Code in Types 100% Covered" Unit="LoC" />
Application.Types.Where(t => t.PercentageCoverage == 100)
.Sum(t => t.NbLinesOfCodeCovered)
//<Desc>
// A covered line is *even more valuable* in a type 100% covered. Covering
// 90% of a class is not enough: the 10% uncovered is hard-to-test, hence
// not well-designed, hence error-prone. Better test error-prone code,
// isn't it?
//</Desc>
Open in the interactive Rules Explorer · All default rules
Trend Metrics / Coverage: all 12 items
- Percentage Code Coverage
- # Lines of Code Covered
- # Lines of Code Not Covered
- # Tests
- # Lines of Code Uncoverable
- # Lines of Code in Types 100% Covered
- # Lines of Code in Methods 100% Covered
- Max C.R.A.P Score
- Average C.R.A.P Score
- Percentage JustMyCode Coverage
- # Lines of JustMyCode Covered
- # Lines of JustMyCode Not Covered