I'm finding ways to turn TAP output into something compatible with JUnit. Is there anything to go the opposite direction? I'm writing some JUnit tests and would like to make them output in a way that makes sense to me, possibly going right into some Perl harness code.
Regrettably, there's the problem that the JUnit/TAP models don't play too well together. I would recommend that you treat each test method as one test result in TAP and don't emit a plan until the end. You lose a lot of granularity that way, but at the end of the day, you still get the OK/NOT OK distinction.
