Thanks for the explanation. At my current customer, we use Maven 1, so haven't tried it. I have read the Patchwork docs, and am very intrigued by the solution to the misleading "100%" coverage. I would switch them to Patchwork for that reason, if it proves to work very well as you evolve it (and a Maven 1 plugin exists! :-). It is a huge system, with over 11,000 classes across all components, so the tools need to work well.
Have you thought of joining Cobertura and enhancing it to do that (or is that an uphill battle, not easily possible due to design, etc.), vs continuing to make a another one? There are pros and cons to everything, and I wonder your thoughts on that... -----Original Message----- From: Arnaud Bailly [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 1:44 AM To: Maven Users List Subject: Re: [ANN] First release of Patchwork coverage maven plugin "Jeff Jensen" <[EMAIL PROTECTED]> writes: > I could not find docs on the "3 columns" of the patchwork.html report (what > are the values of each column?). Do you have a doc page on that? > col 1 = total number of "blocks" executed (useful to know which method is most often used) col 2 = maximum number of coverage unit for method/class/package (ie. edges or nodes) col 3 = number of coverage unit actually covered col 4 = coverage percentile I will update documentation asap. > I am very interested in solving the misleading "100% coverage" report of > existing tools. If patchwork can really do that, you have a big hit > underway. > Did patchwork work for you ? regards, -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
