Paul Johnson wrote:
On Tuesday the first [insert desired time period here] Devel::Cover hackathon
was held at the hacker kitchen (aka clkao's flat), sponsored by Best
Practical.
[snip]
So all in all, a very productive and enjoyable day. Lots and lots of thanks
to everyone.
Productive ind
I'm confused - was this a hackathon, or Iron Chef ?
L
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 3 August 2006 11:57 PM
To: perl-qa@perl.org
Subject: Devel::Cover hackathon
On Tuesday the first [insert desired time period here] Devel::Cover hac
On 3 Aug 2006, at 14:40, Michael Peters wrote:
[snip]
Actually, the way I use Test::Class is to have one script per
class. That way I
can just run one if I want to.
Yeah - but then you lose the start up time advantage when you run
multiple classes in the same process.
(not that it's a ba
On Tuesday the first [insert desired time period here] Devel::Cover hackathon
was held at the hacker kitchen (aka clkao's flat), sponsored by Best
Practical.
I think the day was a great success. We had a bunch of commits comprising bug
fixes, new functionality and refactoring, culminating in the
On 3 Aug 2006, at 14:20, Ovid wrote:
What I would prefer to do is something like this:
prove t/test_class_tests.t path/to/test/class.pm
for consistency with perl maybe add a -M option to prove so you could
have:
prove -Ipath/to -Mtest::class t/test_class_tests.t
?
Adr
Ovid wrote:
> Hi all,
>
> This is probaby a weird request and it's something I could use, but not
> everyone will. Further, it might require that Test::Harness be changed and I
> don't know if this is likely or reasonable.
>
> Basically, when I run a single test, I do something like this:
>
Hi all,
This is probaby a weird request and it's something I could use, but not
everyone will. Further, it might require that Test::Harness be changed and I
don't know if this is likely or reasonable.
Basically, when I run a single test, I do something like this:
prove t/test_name.t
Howeve
