# from Jonathan Swartz
# on Friday 26 October 2007 14:49:
>This is for thirty test classes, so there's about 2 seconds of load
>overhead per class.
That's "per class + process". What's the time required to load them all
in one process and then quit before testing anything?
Now subtract that
chromatic wrote:
On Friday 26 October 2007 13:05:14 Tom Heady wrote:
The method does require a single file per class, and loading perl
for
each of those files. If you are trying to avoid that it's not
going to
help.
... and if that's the slowest part of 45-minute test runs, color
me
chromatic wrote:
> On Friday 26 October 2007 13:05:14 Tom Heady wrote:
>
>> The method does require a single file per class, and loading perl for
>> each of those files. If you are trying to avoid that it's not going to
>> help.
>
> ... and if that's the slowest part of 45-minute test runs, colo
On Friday 26 October 2007 13:05:14 Tom Heady wrote:
> The method does require a single file per class, and loading perl for
> each of those files. If you are trying to avoid that it's not going to
> help.
... and if that's the slowest part of 45-minute test runs, color me surprised.
-- c
The problem that I was mentioning is having to explicitly call each
class in a separate file. The method below keeps that from happening.
I assumed you were talking about programmer efficiency. (DRY)
The method does require a single file per class, and loading perl for
each of those files. I
So this is a single file? And when you say you are getting around the
problem, you mean having to define a whole other script per class?
Because it still looks like you have to launch Perl and load your
modules for every test class.
On Oct 26, 2007, at 10:39 AM, Tom Heady wrote:
Jonathan
Jonathan Swartz wrote:
...
I'd like to avoid actually running a single script per class, for
efficiency reasons - i.e. I agree with Ovid and Adrian here:
http://use.perl.org/~Ovid/journal/31172
...
I get around the problem described in that post thusly:
foo.t:
--
#!/usr/bin/perl
# from Jonathan Swartz
# on Friday 26 October 2007 06:53:
>I'd like to avoid actually running a single script per class, for
>efficiency reasons - i.e. I agree with Ovid and Adrian here:
> http://use.perl.org/~Ovid/journal/31172
>
>It seems like it should be possible (easy?) to create a new
On 26 Oct 2007, at 17:54, Jonathan Swartz wrote:
In the alpha version of Test::Harness, yes. I also see that
runtests has become prove in TH3.
btw, in Test-Harness-2.99_04, prove's documentation contains this:
=head1 SEE ALSO
C, which comes with L and whose code I've
nicked in a few pl
On Oct 26, 2007, at 9:39 AM, Andy Armstrong wrote:
On 26 Oct 2007, at 17:36, Jonathan Swartz wrote:
Would it be easier to write a subclass of TAP::Harness and use
runtests, instead of Test::Harness and prove? I confess that I'm
still a little confused about the relationship between the two
On 26 Oct 2007, at 17:36, Jonathan Swartz wrote:
Would it be easier to write a subclass of TAP::Harness and use
runtests, instead of Test::Harness and prove? I confess that I'm
still a little confused about the relationship between the two going
forward.
Test::Harness exists only as a comp
On Oct 26, 2007, at 6:50 AM, Michael Peters wrote:
We use Test::Class a lot too and we do indeed write a separate
script for each
testing module.
I dislike the latter solution for its inefficiency, as Perl
and all our common modules would have to be loaded many times. Our
test suite already
On 26 Oct 2007, at 14:50, Michael Peters wrote:
Just remember that to use Smolder you need a TAP Archive, so you'd
have to have
prove use both the T::C and the Archive modules. I'm not sure how
the plugin API
has settled (or if it even has) and whether or not it is currently
possible to
hav
We use Test::Class for all our tests, with a single script (_t.pl)
that automatically loads and runs all test classes.
Unfortunately, with prove and the standard test harness, this causes
test output in which all tests are listed under a single script.
/home/swartz/env/hm/lib/HM/t/_t...
cc'ing perl-qa for input
Jonathan Swartz wrote:
> We use Test::Class for all our tests, with a single script (_t.pl)
> that automatically loads and runs all test classes.
>
> Unfortunately, with prove and the standard test harness, this causes
> test output in which all tests are isted under
15 matches
Mail list logo
