Hi, today I spent a couple of hours setting up my test script to output JUnit, to run them under Hudson.
This experience was mostly pain free. I started with the tap-to-junit script but then switched to the TAP::Harness::JUnit to get a prettier JUnit report. All the process got me thinking about Test::Builder. I spent a couple of hours tonight trying to see how would I output JUnit with TB2. I tried to write a Formatter::JUnit and was mostly successful, but I could not see how TB2 ties into the current TAP::Harness stack, that powers App::Prove. I don't know all the pieces that well yet, but seems to me that TB2 has no need for formatters. Those should be at the Harness level. TB2 scripts would generate a more robust stream of TAP events, and the TAP2::Harness would feed them into one or more formatters to produce the file format. Right now, I failed to see how would a Harness module would even setup a different format for the test scripts, given that the TB2 setup happens in a different process space, after a IPC::Open3 call in the TAP::Parser::Iterator::Process. I'm sure I'm missing something and there is a plan to glue the Harness with TB2 formatters. If some kind soul could take a little bit of time to point me in the right direction (maybe there is a TAP2 tree somewhere?), I could go and look and try to make use of my hacked TB2::Formatter::JUnit. Thanks, -- Pedro Melo http://www.simplicidade.org/ xmpp:m...@simplicidade.org mailto:m...@simplicidade.org
