Hi there,
2009/4/21 Saftoiu, Rares rares.saft...@neustar.biz:
I was wondering if there were any tools available for doing continuous
integration with perl. I basically need something that will watch a
directory, merge any branches from the directory into trunk, run unit tests,
and email the
2009/3/27 Ovid publiustemp-perl...@yahoo.com:
I've asked what people would like to see from the Perl-QA hackathon:
http://use.perl.org/~Ovid/journal/38709
Answer there if you have an account. Otherwise, answer here :)
I don't know if there'll be time for non-hacking stuff, but I'd love
to
Hello,
On Feb 4, 2009, at 10:35 PM, Ovid wrote:
Thoughts on first order support:
use Test::More;
plan(3);
pass;
pass;
pass;
plan(2)
pass;
pass;
done_testing() # optional
I just made a branch of Test::Builder which does this. You can see the
expected behaviour in the tests at:
Hey,
On Jan 28, 2009, at 5:19 PM, Ovid wrote:
That being said, 'not ok - test exited prematurely' is not terribly
structured and doesn't necessarily let an advanced TAP consumer
present this information any better.
As I understand it, the idea behind the final 'not ok' isn't as an
Hi everybody,
On Jan 23, 2009, at 3:22 PM, Ovid wrote:
Well, since the thread was about Eric's method of eliminating
'plan', after you made your explanation, I think it was clear that
the proposal would require, as Eric suggested, an alteration to core
TAP:
ok 1
ok 2
ok 1
ok
Hi everybody,
2008/10/8 Ovid [EMAIL PROTECTED]:
We understand what a lot of basic issues are, so let's get some traction on
this.
As the next thing we need is a group charter (if we already have one,
and I just haven't noticed, ignore this e-mail), I've copied the
charter format from RFC 2418
Hi,
2008/9/12 David Landgren [EMAIL PROTECTED]:
Barbie wrote, some time around 11/09/2008 16:19:
Today I'm pleased to announce the launch of the CPAN Testers' Collated
Email Notification of Tester Reports for Authors Service [1], a
Hmm, L is always a bit of a bastard to backronymise
It sends
