Test::Harness features

[Steve Purkis]

On 17 Jun 2009, at 12:32, Andy Armstrong <andy at hexten.net> wrote:

> On 17 Jun 2009, at 09:32, Steve Purkis wrote:
>>
>>> TAP:: might be a rather poor namespace because if someone wants to
>>> read POSIX test results, they can't.  And we can't even *dream* of a
>>> mixture of those.  But let's ignore the namespace for just a
>>> moment.  Given rather confused state of the testing world in regards
>>> to standardizing output, we have a unique opportunity to:
>>>
>>> TAP::Parser::Grammar::TAP
>>> TAP::Parser::Grammar::Ant
>>> TAP::Parser::Grammar::POSIX
>>> TAP::Parser::Grammar::TestNG
>>> ... and so on
>>
>>
>> Agreed on the namespace, that aside: so you're suggesting having
>> pluggable grammars as well?
>>
>> That complicated things.  I can see the benefit though.
>
>
> The whole of TAP::Harness is about TAP - I don't think that just
> plugging in a new grammar is going to work. Instead, how about:
>
>    Test::Harness::The::World
>        TAP::Harness
>        TestNG::Harness
>        etc
>
> In other words we need a new layer at the outside which wraps
> different test runners.

Not quite the same as it'd be harder to map sources to grammars at run  
time.

But frankly, using external wrappers would make our lives a lot  
easier.  And is on topic for the list ;-)

TBH I'm happy with either approach, so long as we all agree on it.  if  
I had to choose I'd say: somebody else's problem. Let TAP:: focus on  
things that consume TAP.

-Steve