where we use Test::ParallelSubtest which provides a
simple interface to run test steps in parallel.
Regards,
Jan
From: Ovid [mailto:curtis_ovid_...@yahoo.com]
Sent: Wednesday, January 15, 2014 3:53 AM
To: Jan Seidel; perl-qa@perl.org
Subject: Re: New Test::Builder version broke Test
Hi Jan,
For running multiple tests in parallel, I'm not sure if there is a
recommended alternative, but the two which immediately sprint to mind are
Fennec, by Chad Granum[1] and my Test::Class::Moose module[2], using the
parallel role[2]. I've also uploaded a new slide deck for
On Tue, Jan 14, 2014 at 12:55 AM, Jan Seidel jan.sei...@skyera.com wrote:
Have you contacted the author? It doesn't look to me like you filed a
bug report. Odds are this is something that could easily be fixed.
Leon
Thanks for the recommendation, I opened a bug. I initially skipped this as
On Tue, Jan 14, 2014 at 12:30 AM, Jan Seidel jan.sei...@skyera.com wrote:
Hi,
I’m using the Test::ParallelSubtest module to run multiple tests in
parallel. However, a change in Test::Builder now broke this module. Every
bg_subtest block fails with an error like the following:
not ok 1
On 1/13/14 6:55 PM, Jan Seidel wrote:
I initially skipped this as I saw another open bug that hasn't been addressed
since 2 years now. But I agree that for tracking purposes it is nonetheless a
good idea to open a bug:
https://rt.cpan.org/Public/Bug/Display.html?id=92119
Heh! Even much
On 15 Jan 2008, at 11:18, Ovid wrote:
[snip]
* Make it subclassable.
* Allowed deferred plans.
* Allow for TAP upgrades (YAMLish, YAMLish, YAMLish!).
* On Fail callbacks? (I realize lots of people will squawk here)
* [insert your desired features here]
Don't get hung up on the On
On 15/01/2008, Ovid [EMAIL PROTECTED] wrote:
Test::Harness used to be very limited. We couldn't do a lot with it,
but when we started testing, most of us didn't do a lot with it. As we
understood more about testing, we understood better many things we
wanted. As a result, Schwern posted a
Test::Harness used to be very limited. We couldn't do a lot with it,
but when we started testing, most of us didn't do a lot with it. As we
understood more about testing, we understood better many things we
wanted. As a result, Schwern posted a great plan for rewriting
Test::Harness. It worked
Ovid wrote:
Test::Harness used to be very limited. We couldn't do a lot with it,
but when we started testing, most of us didn't do a lot with it. As we
understood more about testing, we understood better many things we
wanted. As a result, Schwern posted a great plan for rewriting
