Perl best practices @ CIT
My colleague Tim Brown hosted a discussion around best practices for perl testing.
I was taking notes of the thread and it’s now available on The CIT wiki:
http://www.citconf.com/wiki/index.php/PerlBestPractices
Feel free to comment on this post to followup, correct, extend what has been written.
RE: http://www.citconf.com/wiki/index.php/PerlBestPractices
I saw the comment about integrating CrusieControl with Perl’s testing frameworks. My team is trying do exactly the same thing. Can you elaborate on that a bit? Do you have a custom test harness that emits XML instead of TAP? I haven’t been able to find a formal specification for the JUnit’s XML format — do you know what it is? Thanks for your time.
-Jeff
Hi Jeff,
Andrew P. hasn’t given any details on how he implemented the integration between perl and Cruise Control.
JUnit itself doesn’t output xml, AFAIK, but Cruise Control has something called a “build loop”.
This is where cruise control does all the things it has to do and output the results as an XML build log.
My understanding is that Andrew transformed the TAP output (maybe using Test::TAP::Model::File) into the same XML as the build log.
After looking at some sample build logs, the xml format seems very close to Ant XML format which is not a surprise as Cruise Control is a wrapper around the Ant build system.
Maybe a look at the Ant documentation will give you the spec.
Although our talk was not centered around CC integration, my interest in seeing a perl-CC integration has increased since. But a better knowledge of Ant is required first.