Search the Confluence 4.1.x Documentation:

Index
Downloads (PDF, HTML & XML formats)
Other versions

This documentation relates to Confluence 4.1.x
If you are using an earlier version, please view the previous versions of the Confluence documentation and select the relevant version.
Skip to end of metadata
Comment: Corrected links that should have been relative instead of absolute.
Go to start of metadata

 

The JUnit Report macro displays a summary of JUnit test results from a directory accessible by the Confluence server. JUnit is a unit testing framework which allows programmers to ensure that individual units of Java source code are functioning correctly.

The JUnit Report macro appears as shown in the screenshot below.

Screenshot: The JUnit Report macro in Confluence

(info) When generating reports from the JUnit Report macro, set the Apache Ant formatter to 'XML'.

Using the JUnit Report Macro

To add the JUnit Report macro to a page:

  1. In the Confluence editor, choose Insert > Other Macros.
  2. Find and select the required macro.

Parameters

When editing, you can click on the macro placeholder and choose Edit to display the parameters for this macro in the Macro Browser.

Parameters are options that you can set for Confluence macros to control the content or format of the macro output. The table below lists parameters for this macro that can be set in the Macro Browser.

Parameter

Default

Description

URL of the test result XML file

None

URL of a particular test result XML file. Is overridden by the Directory (URL) of your test result files parameter if you use both.

Example, from a Confluence instance: http://yourConfluenceInstance.com/download/attachments/<page id>/file.xml

For Confluence installations without anonymous user access, you can specify logon credentials as part of this parameter in the form of URL parameters:

  • os_username — The username of a Confluence user with permission to access to the JUnit test results.
  • os_password — The password of the Confluence user specified in the os_username parameter.

Directory (URL) of your test result files

None

URL of a directory containing your test result files. This must be a directory name and not the XML file itself. Overrides the URL of the test result XML file parameter if you use both.

Example, for a local drive: file:///C:/TEMP/

Example, for a network drive: http://*host*/*path*

Report Detail

all

Detail for the report. Can be all, fixture, summary or failuresonly.

Debug

None

Shows the content of failures, as well as the error messages.

Related Topics

Working with Macros

Take me back to the Confluence User's Guide.

Labels:
None
Edit Labels

5 Comments

Hide/Show Comments

  1. May 05, 2011

    Anonymous

    Hi,

    I use an automated testing tool which produces as well JUnit xml reports - as output. However, if there is any of test cases failing, the report fails to show on a Confluence page, using

    junitreport: Error parsing JUnit report file: java.net.MalformedURLException: no protocol:
    macro. In case all tests pass, the output is printed correctly.

    Snippets from the JUnit output report, containing errors

    Can you please tell me details about the parser of junitreport macro? Or an example of a "correct" xml file? Or what's wrong in the above example? If I take out the testsuite containing the <error> tags - report will be successfully printed, if I put them back - nothing is shown on Confluence page, not even an error message.

    Thanks for your help.

    1. May 31, 2011

      Jonas B. Nielsen

      Hello,

      Did you add the macro by clicking the little macro icon in the editor? I am no expert and I do not no the origins

      of the error message, but perhaps you need to check whether the macro is available at all, this can be done

      by using the graphical wizard described here.

      jonasbn

  2. May 31, 2011

    Jonas B. Nielsen

    I would love to see a Hello World like example of how this works. I can get the report to render something not

    resembling the actual test results but more a default template, so I wonder if the JUnit report format I use is

    different from the expected?

    Feel free to browse: The Confluence instance where it is used or the actual report XML file

    The report does hold more than one suite, but I have not seen any examples indicating that this is not allowed.

    1. Jun 01, 2011

      Jonas B. Nielsen

      It seems the macro does not support multiple test suites in a single file. I am currently evaluating the XSD,

      but I am very unsure whether the XSD I am looking at is contemporary (ref: http://glite.cvs.cern.ch/cgi-bin/glite.cgi/org.glite.testing.unit/config/). I have changed the contents of the XML file mentioned above, so it does not

      have the wrapping testsuites tags and multiple testsuite tags and then it works like a charm. My only issue with

      this is that I need to change the whole continuous integration set up to split output into single files and I am not

      sure this is the best way since the rest of my toolchain seems to have no issues.

      1. Jun 07, 2011

        Edwin Dawson [Atlassian Technical Writer]

        Hi there Jonas,

        Unfortunately I can't help you with this particular issue, but you might want to consider posting a question on Atlassian Answers. There, more people are watching the discussions and could well have the information that you need.

        You could also create a feature request on our issue tracker for the Confluence developers.

        Alternatively, you could always open a support request at http://support.atlassian.com, where our support engineers will be able to get back to you quickly.

        I hope this helps.

        Best Regards,

        Edwin Dawson
        Technical Writing Team Leader
        Atlassian
        http://www.atlassian.com