On Fri, Mar 04, 2005 at 04:44:42PM -0800, Ofer Nave wrote:
> Michael G Schwern wrote:
>
> >On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
> >
> >>Random thought: Could Devel::Cover be automatically run against all
> >>modules in CPAN, with ratings posted on cpan.org right next to the
It occurs to me that the Test::* and ExtUtils::* modules should be the
first stop for the Phalanx project. :)
That's why there are a bunch of 'em listed up at the top of the P100.
Incidentally, is it acceptable for an author to Phalanx-review his own
module
Sure, but you should be doing that any
On Fri, Mar 04, 2005 at 04:44:42PM -0800, Ofer Nave wrote:
> Is it possible to tell quasi-reliably if the code in question uses
> threads and skip it? On that note, is forking also problematic?
Not really. Anywhere within the test or any code called by the test might
use threads. Devel::Cover
Abe Timmerman wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
Looking for something like this:
http://pjcj.sytes.net/cpancover/
(The link is available from http://qa.perl.o
Michael G Schwern wrote:
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
It still chokes on certain not uncommon constructs
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
> Random thought: Could Devel::Cover be automatically run against all
> modules in CPAN, with ratings posted on cpan.org right next to the usual
> test results?
It still chokes on certain not uncommon constructs like threads.
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank
you). His patch fixed a bug where all tests printed error diags even
if they passed. Additional tests were added to ensure that no output
is sent from diag in success
