Test counts
Andy Armstrong
andy at hexten.net
Sun Nov 18 17:13:08 EST 2007
On 18 Nov 2007, at 20:46, Ovid wrote:
> And every time TAP::Parser->new is called, it would increment its
> current test count by one (this would make it work with parrallel
> tests, right?).
TAP::Parser being the place to store this info so it's available to
the formatter?
Could TAP::Harness just tell each new TAP::Parser "you are parser 16
of 84"? And have the harness do the counting?
I've been looking at that code today for another reason. I've been
playing around with Test::Steering - which currently runs nested tests
and massages the TAP output into a single stream and which will - I
hope - be able to take advantage of structured TAP at some point in
the future.
That gives us a use case for wishing to run the same test more than
once:
$ENV{bibble} = 'froon';
include_tests( 'xt/opt/spangler.t' ); # froon spangler
$ENV{bibble} = 'bare'
include_tests( 'xt/opt/spangler.t' ); # bare spangler
Which is a little like the problem you described the other day.
Currently the aggregator chokes if you feed it more than one test with
a particular name. I'd like to make it possible to specify a test
either as the name of a script (as currently):
$harness->runtests( 'xt/opt/spangler.t' );
or as the name of a script and a description:
$harness->runtests( [ 'xt/opt/spangler.t', 'froon spangler' ],
[ 'xt/opt/spangler.t', 'bare spangler' ] );
Mentioned apropos of not much - just thinking out loud really :)
[1] http://search.cpan.org/~andya/Test-Steering/
--
Andy Armstrong, Hexten
More information about the tapx-dev
mailing list