Re: fork and tests: making it easier

2012-08-04 Thread Michael G Schwern
On second thought, this has to be turned on explicitly for implementation reasons, so there's no backwards compat issue. "use Test::SharedFork" would simply turn on that feature in Test::Builder 1.5 providing a way to smoothly transition between 0.9x and 1.5. See https://github.com/schwern/test-m

fork and tests: making it easier

2012-08-04 Thread Michael G Schwern
Executive Summary: I propose Test::Builder 1.5 makes writing tests using fork as easy as writing tests using threads is. Test::Builder will handle the coordination for you. Downside: this breaks existing behavior. Rebutal: if you're testing with fork your tests are probably broken with Test::Bu

Test::Builder::Tester considered harmful. Use Test::Tester.

2012-08-04 Thread Michael G Schwern
Executive Summary: If you're using Test::Builder::Tester to test your Test module, switch to Test::Tester. It will make the transition to Test::Builder 1.5 smoother and avoid future breakage due to TAP formatting changes. A lot of the work done fixing CPAN Test::* modules to be compatible with Te

Re: Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread Paul Johnson
On Sat, Aug 04, 2012 at 12:19:18PM -0400, James E Keenan wrote: > On 8/4/12 11:34 AM, James E Keenan wrote: > >On 8/4/12 11:16 AM, James E Keenan wrote: > >>On 8/4/12 10:54 AM, Paul Johnson wrote: > >>How did you generate > >>>your coverage report? > >>> > >> > >>Main part of my shell script: > >>

Re: Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread James E Keenan
On 8/4/12 11:34 AM, James E Keenan wrote: On 8/4/12 11:16 AM, James E Keenan wrote: On 8/4/12 10:54 AM, Paul Johnson wrote: How did you generate your coverage report? Main part of my shell script: cd $SOURCEDIR && \ cover -delete $COVERAGEDIR && \ PERL5OPT=-MDevel::Cover=-db,$COVERAGEDIR/ \

Re: Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread James E Keenan
On 8/4/12 11:16 AM, James E Keenan wrote: On 8/4/12 10:54 AM, Paul Johnson wrote: How did you generate your coverage report? Main part of my shell script: cd $SOURCEDIR && \ cover -delete $COVERAGEDIR && \ PERL5OPT=-MDevel::Cover=-db,$COVERAGEDIR/ \ perl Makefile.PL && make && make test && \

Re: Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread James E Keenan
On 8/4/12 10:54 AM, Paul Johnson wrote: How did you generate your coverage report? Main part of my shell script: cd $SOURCEDIR && \ cover -delete $COVERAGEDIR && \ PERL5OPT=-MDevel::Cover=-db,$COVERAGEDIR/ \ perl Makefile.PL && make && make test && \ cover $COVERAGEDIR \ -coverage sta

Re: Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread Paul Johnson
On Sat, Aug 04, 2012 at 08:54:27AM -0400, James E Keenan wrote: > When I run Devel::Cover over the Test::Builder2 test suite > (v1.005000_001-193-g00d4609), I get no coverage reports for > blib/lib/Test/Builder2.pm or blib/lib/Test/More.pm. > > See: http://thenceforward.net/test-more/coverage/cov

Test::Builder2: running coverage fails to display key modules

2012-08-04 Thread James E Keenan
When I run Devel::Cover over the Test::Builder2 test suite (v1.005000_001-193-g00d4609), I get no coverage reports for blib/lib/Test/Builder2.pm or blib/lib/Test/More.pm. See: http://thenceforward.net/test-more/coverage/coverage.html Any thoughts on why that is happening? Thank you very much