[tap-l] What's the best way to do logging?

[Michael Moore]

> Andy Armstrong wrote:
> On 14 Nov 2007, at 20:53, Michael Moore wrote:
>> Since we want to use these tests for some time, I'd like to move to
>> something that's not discontinued. Could someone here tell me if
>> TAP::Harness and TAP::Parser is what I should be looking at?
> 
> Yes. By design TAP::* replaces the existing Straps mechanism. If it  
> won't do what you want it to do we need to log at that design.

Great. As I've been looking into more, it looks like it'll be even
better than Test::Harness. In particular, it looks like it's easier to
get the results of tests out of TAP::Parser.

>> Is TAP::Harness and TAP::Parser what I should be looking at? Or is  
>> there
>> an easier way to do logging?
> 
> I think TAP::Harness is the way forwards. Michael Peters wrote  
> TAP::Harness::Archive[1] which is designed to capture everything from  
> a test run. It's used to upload test results to Smolder[2] - which may  
> also be of interest to you.
> 
> Unfortunately the latest release of Test::Harness has broken  
> T::H::Archive. There's a fixed version in the Test::Harness subversion  
> repo - I guess I need to give Michael a poke. In the mean time you can  
> get the latest version here:
> 
>    http://svn.hexten.net/tapx/TAP-Harness-Archive/trunk/
> 
> May I suggest that you start by reading the documentation for  
> TAP::Harness::Archive and see if that might do what you want?
> 
> [1] http://search.cpan.org/~wonko/TAP-Harness-Archive/
> [2] http://sourceforge.net/projects/smolder

Thanks I hadn't see TAP::Harness::Archive. It doesn't do exactly what I
need, but it was very useful as a reference. With is as an example, I
was able to get a sample test working with TAP::Harness.

Looks like it's going to do what we need. TAP::Harness here we come.

Thanks again,
Michael Moore