Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Oslo Perl QA Hackathon 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • hey, re this -- I don't know if you saw this on Planet Perl, but I recently hacked up a conversion script for the other direction:

    http://jmason.org/software/scripts/tap-to-junit-xml.txt [jmason.org]

    head1 NAME

    tap-to-junit-xml - convert perl-style TAP test output to JUnit-style XML

    =head1 SYNOPSIS

    tap-to-junit-xml "test suite name" [ outputprefix ] ) format, and produce XML output in a similar format to that produced by the ant task. This is useful for consumption by continuous-integration systems like Hudson (C).

    thanks for working on getting TAP into a well-defined standard format, guys. I've been dealing with a lot of JUnit-style formatting recently, and I miss TAP ;)
    • damn, guess who forgot to preview. ;)

      here's the missing text:

      =head1 SYNOPSIS

      tap-to-junit-xml "test suite name" [ outputprefix ] < tap_output.log

      =head1 DESCRIPTION

      Parse test suite output in TAP (Test Anything Protocol, http://testanything.org/ [testanything.org] ) format, and produce XML output in a similar format to that produced by the junit ant task. This is useful for consumption by continuous-integration systems like Hudson ( https://hudson.dev.java.net/ [java.net] ).
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.