--- Tels <[EMAIL PROTECTED]> wrote: > > So I think a spin-off of Test::Harness which will facilitate doing > that > > is still in order. > > Why not fix Test::Harness instead of re-inventing it entirely?
That's my thought. It's been known for a long time that Test::Harness works well, but only for the specific task it's been designed for. There's been a lot of discussion about improving/extending it. This is a much better solution than making a fork for a feature that's likely not compelling enough for folks to make the switch. Don't get me wrong. I also want color highlighting of test code. However, there's a lot more stuff I would like to do with the test output (imagine a Wx extension that provides the red/green color bars that JUnit provides). By fixing Test::Harness, we get a more general case solution and everybody wins. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
