[tapx-dev] Test::Harness 3.0

[Andy Armstrong]

On 23 Jul 2007, at 19:04, Andy Dougherty wrote:

> On Mon, 23 Jul 2007, Andy Armstrong wrote:
>
>> On 23 Jul 2007, at 18:01, Andy Dougherty wrote:
>>> It wasn't my intention to test TAP::Parser.  Based on the subject  
>>> line, I
>>> wanted to test Test::Harness 3.0, which supposedly fixes most of  
>>> the bugs
>>> in the Test::Harness RT queue.  I wanted to point out that it  
>>> doesn't fix
>>> this bug.
>>
>> But you're not testing Test::Harness 3.0 because it doesn't exist.  
>> And you're
>> not testing TAP::Parser (which is T::H 3.0 in waiting) because  
>> you're just
>> running your test through the existing Test::Harness along with  
>> all of
>> TAP::Parser's tests.
>
> I think I'll just wait until Test::Harness 3.0 exists, then.   
> Perhaps then
> I'll see how all the pieces fit together.

Sheesh! :)

Once more:

* TAP::Parser (inc TAP::Harness) is the code that will become
   Test::Harness 3.0
* any version of Test::Harness you have installed now is *not*
   TAP::Parser / T::H 3.0
* the test suite for TAP::Parser runs through whatever Test::Harness
   you have installed on your system - just like most other modules'
   test suites
* when you added your test case to TAP::Parser's test suite you were
   just running it through the existing Test::Harness - just like all  
the
   other TAP::Parser tests
* If you install TAP::Parser you will also get TAP::Harness and you can
   easily run tests through it with the runtests command
* Running your test with runtests shows that TAP::Parser produces
   sensible output for it - ergo the bug is fixed in TAP::Parser

OK? :)

-- 
Andy Armstrong, hexten.net