> On 11/07/2012 03:51 PM, Jonathan Swartz wrote: >> Now on cpan. A much simpler solution than what I suggested :) and apparently >> still works with parallel testing. Thanks miyagawa! >> >> https://metacpan.org/module/forkprove > > I did some benchmarking last night and found no real benefit over prove > -j, but Miyagawa reports that "heavy" modules like Catalyst and Moose, > he's seen 40% to 50% speed-ups. > > See the details of our discussion on Github: > > https://github.com/miyagawa/forkprove/commit/ca2b0c2f55a250468c4f61f7cbd1b008a0eb91b4#commitcomment-2115186
I wasn't able to get forkprove to work with Test::Class, because of Test::Class's insistence that tests be declared at compile time. swartz> cat t/Sanity.t #!/usr/bin/perl use CHI::t::Sanity; CHI::t::Sanity->runtests; swartz> forkprove t/Sanity.t t/Sanity.t .. Test::Class was loaded too late (after the CHECK block was run). See 'A NOTE ON LOADING TEST CLASSES' in perldoc Test::Class for more details t/Sanity.t .. No subtests run Mark, you mentioned before that you use Test::Class before - did you use it in conjunction with forkprove? If this truly can't work, it may be the straw that finally gets me away from Test::Class, or at least to use Test::Class::add_testinfo instead of the subroutine attributes.
