Andy Armstrong wrote:
> On 21 Dec 2007, at 00:11, Michael G Schwern wrote:
>> This could be accomplished silently with some environment variables.
>> TAP_PARSER_ARCHIVE_DIR=/path/to/somewhere
>
> It's called PERL_TEST_HARNESS_DUMP_TAP and it already exists.
Well there you go.
Though might I suggest that...
A) This be documented in Test::Harness, I note it's only in
Test::Harness.
B) The TAP::Harness version be changed to PERL_TAP_HARNESS_DUMP_TAP. Don't
want Test::Harness features leaking into TAP::Harness.
C) The Test::Harness version be changed to HARNESS_DUMP_TAP (to match all
the other environment variables)
All that HARNESS_DUMP_TAP would do is twiddle the appropriate TAP::Harness bit.
I also note that setting the environment variable appears to be the *only* way
to get this behavior. It would be handy if there was a normal parameter to
set it.
If I can sort out my SVK breakage I'll get on it.
>> There is the problem of getting TAP::Parser to recognize that the archive
>> feature is available and that gets back to the open TAP::Builder problem.
>
> I don't understand...
Sorry, I thought an optional plugin/subclass was necessary to get TAP::Harness
to save TAP. Didn't realize it's built in.
--
If at first you don't succeed--you fail.
-- "Portal" demo
