[tapx-dev] Test::Harness 3.0 roadmap

[Michael G Schwern]

Ovid wrote:
> Interestingly, that's probably the number one issue.  Here's a TODO
> list :)
> 
>   http://rt.cpan.org/Public/Dist/Display.html?Name=Test-Harness
> 
> There are 65 items, many of them are spam.  Andy, can you clear any of
> those or at least get rid of the spam?

Done.



>> * The one open ticket, 24728 is fixed. Could you mark it closed  
>> please Curtis?

*snip*

> 'runtests' still spits out the diagnostic unless we include the '-q'
> switch.  I do not think, with the current implementation, that we can
> "fix" this to exactly mimic the behavior of the current test harness. 
> Mark it as 'resolved' but with said explanation?

How is that resolved?  There's not even a work around.  -q doesn't count
because...

  Thu Feb 01 15:31:31 2007  	 MSCHWERN - Correspondence added

  I tried --quiet but unfortunately it turns off diagnostics on both
  STDOUT and on STDERR thus supressing failure output along with
  informational output.

Its ok to leave a ticket open that you can't immediately fix.  However, this
is going to be a big issue with Test::Harness 3.0.  Comments going to STDOUT
do not and have never been displayed and suddenly there's going to be a
whole lot of noise that wasn't there before.  IMO its a show stopper.

For some strange reason it doesn't apply to diagnostics coming from TODO
tests, just direct prints to STDOUT.  Are there still Test::Builder
shenanigans going on inside TAP::Parser?


Anyhow, found another issue.
http://rt.cpan.org//Ticket/Display.html?id=25405