Two days ago or so I posted a blog entry about the new CPANTS metrics.
http://szabgab.com/blog/2008/06/1212827982.html
I am glad that already there are some comments about them
even if both chromatic and Andy Lester are well, slightly against them
and even Ovid did not like the Test::NoWarnings
On Mon, Jun 9, 2008 at 4:32 PM, Gabor Szabo [EMAIL PROTECTED] wrote:
I am sending this to both the module-authors list so you can be
aware of the new metrics and the perl-qa list as they might
have a few words as well regarding kwalitee.
First, I have to say that I applaud and appreciate the
So apparently using Test::NoWarnings isn't that cool
and mandating it with CPANTS metric is even less cool.
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
I wrote it in my blog too but here it is. Occasionally when I install
a module manually I see
On Monday 09 June 2008 21:28:40 Gabor Szabo wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
Is it even possible? I thought one of the goals of CPANTS was not to run any
of the distribution's code directly. The most useful metrics seem to
On Tue, Jun 10, 2008 at 7:42 AM, chromatic [EMAIL PROTECTED] wrote:
On Monday 09 June 2008 21:28:40 Gabor Szabo wrote:
The issue I am trying to solve is how to catch and report
when a test suit gives any warnings?
Is it even possible? I thought one of the goals of CPANTS was not to run any
