On 26 Oct 2007, at 18:05, Eric Wilhelm wrote:
# 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
TAP::Harness that treated each Test::Class class as its own "script"
in the output.
Building it as a TAP::Harness plugin sort-of implies that the tap
stream
contains diagnostics which tie the results to a given class.
[snip]
What I just posted on the Smolder list - just in case folk are
interested here...
---
When the free time fairy next visits what I'd like to do is have T::C
use some of the newer features and push information on the class/name/
tags of the running method out into TAP.
E.g. if something like http://testanything.org/wiki/index.php/
Test_Groups ever gets sorted that would be a natural place to split
separate tests. I also want to do something like:
sub do_real_merge_with_example_data_set_X22 :Tests :Tag(database
slow acceptance) { ... }
not ok 2 - do real merge with example data set X22
---
extensions:
tags: database slow acceptance
which should let test runners cut up the output in useful ways. This
is actually already mostly done :-)
Cheers,
Adrian
