Thanks for the feedback. I'll tackle the second question first: I was hoping monks would simple run the tprove program against some test suites let me know if there were any parse errors. Fortunately, I have a newer version of tprove which should be out soon and will make this easier to do. No coding's required, but it anyone wanted to, I wouldn't complain!
As for the problems with Test::Harness, those are documented here. Even the creators and maintainers of Test::Harness agree that it has to go. Basically, we're talking about code that has evolved over almost 20 years into a big ball of mud. This has led to confused responsibilities within the systems and made it very hard to extend it to add new features.
What do you want to do with that test output? Want colored tests? Want to only report failures? Want to throw them up on a GUI like jUnit and friends? Want to transform them into something your language's test harness can understand? Want them as XML docs? Want to email them? Want to have them run as your wallpaper? Forget it. It turns out that you can do those things, but it's very hard to get right. Attempts to do those things invariably turn out to be buggy and this is because Test::Harness just can't do what we want but simply refactoring Test::Harness becomes difficult because so much code depends upon its globals or other quirks. Heck, if you don't believe me, just look at the bug reports and try to fix a few of those :)
Cheers,
Ovid
New address of my CGI Course.
In reply to Re^2: This is what's wrong with Test::Harness
by Ovid
in thread I need your help with parsing TAP output
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |