Test::Harness
From Perl QA
The venerable Test::Harness, reference implementation for TAP.
[edit] What's wrong with Test::Harness anyway?
In a word: its monolithic.
Test::Harness is the only stable, working TAP parser. Much of TAP is defined in terms of what Test::Harness does. Its not healthy for a protocol to have only one implementation.
Test::Harness cannot be separated out into individual components. The running of tests, parsing of the TAP and display of the results are all intertwined and cannot be separated. Test::Harness::Straps was an attempt to separate the running and parsing from the display, and while its better, it has largely failed to allow users to display TAP results however they like. If you want your results as XML, or emailed, or as HTML, or in a GUI its extremely difficult to do with Test::Harness.
Test::Harness is based on code and concepts almost 20 years old. It evolved from the original t/TEST from perl 1. A very slow process over the last few years has turned it from wholely procedural to partially OO. Its not a very complicated module, it shouldn't take that long.
Test::Harness has nearly a decade of backwards compatibility baggage to anyone trying to improve on it.
