Better description formatting

[Andy Armstrong]

On 22 Aug 2008, at 11:11, Ovid wrote:
>> Isn't that really a request for a change to Test::More?
>> In his
>> examples he's just running the test script directly -
>> Test::Harness  isn't involved.
>
> Hmm, I guess you're right, but don't we do a touch of reformatting  
> of the output?  Now that I stop to think about it, this change  
> wouldn't break TAP in the slightest because by the time it's  
> applied, the TAP would already be parsed.


Yeah, but that doesn't help in precisely the example he uses - running  
his tests without T::H.

We're talking about adjusting the white space between the (not\s+)ok  
and the number. What if someone has arranged for their tests to  
produce output that is already indented in some way?

ok       1 - Load Freeb::Bolk
ok         2 - Init Freeb::Bolk
ok         3 - Spin Freeb::Bolk
ok         4 - Destroy Freeb::Bolk
ok       5 - Load Bolk::Freeb
not ok     6 - Init Bolk::Freeb

We'd then destroy their formatting.

If someone's reading something that looks like TAP that comes from us  
I think it should be as close to the TAP we consumed as possible.

-- 
Andy Armstrong, Hexten