Edgewall Software

Changes between Version 7 and Version 8 of Recipe Commands


Ignore:
Timestamp:
Oct 6, 2005, 6:34:04 PM (19 years ago)
Author:
cmlenz
Comment:

Document <java:junit> and <report>

Legend:

Unmodified
Added
Removed
Modified
  • Recipe Commands

    v7 v8  
    55
    66  ''Note: the recipe format has changed since [milestone:0.4]. You can find documentation about the previous format by looking at version 3 of this page (see the “page history” link above).''
     7
     8----
     9
     10== Generic Commands ==
     11
     12These are commands that are used without a namespace prefix.
     13
     14=== `<report>` ===
     15
     16Parse an XML file and send it to the master as a report with a given category. Use this command in conjunction with the `<sh:pipe>` or `<x:transform>` commands to send custom reports to the build master.
     17
     18==== Parameters ====
     19
     20|| Name || Description ||
     21|| `category` || Category of the report (for example “test” or “coverage”). ||
     22|| `file` || Path to the XML file containing the report data, relative to the project directory. ||
     23
     24Both parameters must be specified.
    725
    826----
     
    125143|| `file` || Path of the build file, relative to the project source directory (default is `build.xml`). ||
    126144|| `target` || Name of the build target(s) to execute. ||
     145|| `args` || Additional arguments to pass to Ant, separated by whitespace. ||
    127146|| `keep_going` || Tell Ant to continue even when errors are in encountered in the build. ||
    128147
     
    134153
    135154Executes the target `compile` of the `build.xml` buildfile at the top of the project source directory.
     155
     156=== `<java:junit>` ===
     157
     158Extracts information about unit test results from a file in [http://junit.org/index.htm JUnit] XML format.
     159
     160==== Parameters ====
     161
     162|| Name || Description ||
     163|| `file` || Path to the JUnit XML test results file. This can include wildcards, in which case all the file matching the pattern will be included. ||
     164|| `srcdir` || Path of the directory unit test sources. Used to link the test cases to files. ||
     165
     166The `file` attribute is required.
     167
     168==== Examples ====
     169
     170{{{
     171 <java:junit file="build/tests/results/TEST-*.xml" srcdir="src/tests" />
     172}}}
     173
     174Collects the test results from all files in the `build/tests/results` directory that match the pattern `TEST-*.xml`. Also, maps the class names in the results files to Java source files in the directory `src/tests`.
    136175
    137176----