[Insight-developers] STEP 1: Code coverage push

[Lorensen, William E (Research)]

Luis,
Luis,

There is a misunderstanding about the coverage listings.

There are three possible line labelings:
a number, says the line has been executed that number of times.
a #, says that the code has been compiled, but not executed
a blank means the line is either not an executable statement or has not been
compiled.

So in the highly untested BinaryMask3DSource, all the code is compiled, but
less than half is tested,

Bill


-----Original Message-----
From: Luis Ibanez [mailto:luis . ibanez at kitware . com]
Sent: Thursday, August 07, 2003 9:16 AM
To: Robert Tamburo
Cc: C. Aaron Cois; Insight Developers List
Subject: Re: [Insight-developers] STEP 1: Code coverage push



Hi Robert,


Yes, 0% is ok   IIF   it is GREEN in the report.

The GREEN files are those that are reasonably
covered OR have few lines uncovered. e.g. a file
with 2 executable lines, which has only one
covered is considered a GREEN file even though
its coverage is just 50%.

The real scary cases are classes like
http://www . itk . org/Testing/Sites/esopus . crd/SunOS-5 . 7-c++/Coverage/__Code_Al
gorithms_itkBinaryMask3DMeshSource_txx.html
with 49% coverage but 1059!!! lines of
uncovered code.

This is 1059 that have NEVER been compiled.

So, it is as covered as the file with 2
executable lines, but I guess everyone
will agree in that 1059 uncovered lines
offer a much bigger risk than 1 uncovered
line.


Thanks for helping in the process of
increasing coverage.



   Luis




----------------------
Robert Tamburo wrote:
> 
> Just to clarify 0.00% is ok if it's GREEN????
> 
> -Rob
> 

_______________________________________________
Insight-developers mailing list
Insight-developers at itk . org
http://www . itk . org/mailman/listinfo/insight-developers