Ovid's code I options as to how I want to run this.
perl -MTest::Harness -e 'runtests(qw(test_Utils.t))'
prove test_Utils.t
make test
L
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, 9 March 2007 11:19 PM
To: [EMAIL PROTECTED]; perl-qa@p
Julien Beasley wrote:
> Well at my last job, we had hundreds of test files.. and most of them were
> really fast because we wanted to keep the total time to a minimum. Even
> then, it took over five minutes to run all of our tests, and that was
> getting to be Too Long. So I could definitely see in
On 9 Mar 2007, at 23:57, Julien Beasley wrote:
Well at my last job, we had hundreds of test files.. and most of
them were
really fast because we wanted to keep the total time to a minimum.
Even
then, it took over five minutes to run all of our tests, and that was
getting to be Too Long. So I
Well at my last job, we had hundreds of test files.. and most of them were
really fast because we wanted to keep the total time to a minimum. Even
then, it took over five minutes to run all of our tests, and that was
getting to be Too Long. So I could definitely see in a case like that that
the ov
On 9 Mar 2007, at 23:39, Julien Beasley wrote:
Thanks Ovid! This may be exactly what I'm looking for (since I'm
going to
have tests in libtap and perl). However, and I apologize if I'm
wrong about
this, doesn't your proposed solution have to start a new perl
interpreter
for every single tes
On Friday 09 March 2007 15:39, Julien Beasley wrote:
> However, and I apologize if I'm wrong about
> this, doesn't your proposed solution have to start a new perl interpreter
> for every single test file? If so, that might up being too slow for
> practical use.
That would surprise me; I would exp
Thanks Ovid! This may be exactly what I'm looking for (since I'm going to
have tests in libtap and perl). However, and I apologize if I'm wrong about
this, doesn't your proposed solution have to start a new perl interpreter
for every single test file? If so, that might up being too slow for
practi
Ovid wrote:
> If you want things to be *really* easy to run test suites in multiple
> languages, do this.
another option is this:
http://people.apache.org/~geoff/test-more-separately.tar.gz
which illustrates how to separate planning, etc in perl but use a
foreign tap producing faile - somethin
If you want things to be *really* easy to run test suites in multiple
languages, do this.
First, make sure that all test programs are executable. Then use this
driver program:
$ cat bin/run.pl
#!/usr/bin/perl
use strict;
use warnings;
my $prog = shift;
unless ( -e $prog &&
