From: <bd...@oc...> - 2006-01-19 09:42:23
|
Geart news there's allready a request ! But maybe a whole column is too much, just a "(LOC covered/LOC non-covere= d)" in the Line Coverage should be enough, like : | 87% (770/884) =3D=3D=3DRed/Green Bar=3D=3D=3D | I don't know your project management processes, do you welcome some help = ? Or can i propose a patch? Ben Selon Mark Doliner <ma...@ki...>: > On Wed, 18 Jan 2006 23:00:46 +0100, benoit wrote > > Hi, > > > > I am using Cobertura and i am wondering why you don't add a column > > "lines of code" like there is "# Classes" or "%". Because when my > > coverage is not good, i would like to see which package/class > > contains the largest number of lines without coverage. Indeed, the > > persentage value is good for overview but not so much to take > > actions ! > > > > The number of lines plus the complexity would be great to > > immediately see where to add tests... > > > > What do you think? > > > > Ben > > I've always thought this was a good idea, but was afraid it would needl= essly > clutter the reports. But I've realized that not showing SLOC sacrifice= s > functionality. We'll probably add a "SLOC" column at some point. FYI = this > is > covered in a feature request on sourceforge: > https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1182500&gro= up_id=3D130558&atid=3D720018 > > -Mark > |