tap2junit1p
Converts tap output to junit
Usage
tap2junit [options]
<filename>
<filename> ...
Options: --suffix
<suffix>
Suffix
for
JUnit
output
files
(default
".xml")
--verbose
Display
verbose
status
during
conversion
--name
<name>
Provide
explicit
name
for
the
JUnit
test
--help/-?
Display
brief
help
message
--man
Display
full
documentation
Overview
"tap2junit" converts TAP output to JUnit.
Give it a list of files containing TAP results and it will create a series of ????.junit.xml output files containing the JUnit representations of that TAP contained in the files.
If you specify - as the filename, "tap2junit" will read from STDIN and write to STDOUT. You may also want to use the "--name" option to name the test explicitly (as the default name of "-" isn't going to make much sense).
Options
-
--suffix <suffix> -
Specifies the suffix which is appended to all of the input files, in order to generate the filename for the JUnit XML file that is being output.
If you want to live dangerously and over-write your original TAP files, you can set this to "" and your original TAP files will be over-written.
Defaults to .xml
-
--verbose -
Display verbose status information during the conversion (telling you which TAP file its working on).
-
--name <name> -
Specifies an explicit name for the JUnit test. If no name is provided, a default name will be constructed based on the full path of the TAP file being processed.
This option has also been aliased as
"--junit_name"to provide compatibility with a patch from Joe McMahon.
--help/-?-
Display brief help message.
-
--man -
Displays the full documentation.
Releases
7 releases since Debian 7 (Wheezy); the text changed 5 times.