Introduction

This package provides an extension to the test runner to the one that ships with zope.testing, as well as a buildout recipe based on zc.recipe.testrunner to install a test script for this test runner.

The test runner is identical to the one in zope.testing, but it is capable of writing test reports in the XML format output by JUnit/Ant. This allows the test results to be analysed by tools such as the Hudson continuous integration server.

Usage

In your buildout, add a part like this:

[buildout]
parts =
    ...
    test

...

[test]
recipe = collective.xmltestreport
eggs =
    my.package
defaults = ['--exit-with-status', '--auto-color', '--auto-progress']

The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details.

When buildout is run, you should have a script in bin/test and a directory parts/test.

To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/reports directory:

$ bin/test --xml -s my.package

Use bin/test --help for a full list of options.

If you are using Hudson, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.

Zope2 'Products' aware

If you still use Zope2 'Products' or you're still on Plone 2.5 and you're tests fail like:

... ImportError: No module named CMFCore.utils

then in your buildout should look like this:

[buildout]
parts =
    ...
    xmltestreport

find-links =
    ...
    http://eggrepo.eea.europa.eu/simple

[versions]
zope.testing=3.9.4
zope.exceptions=3.2.0-eea
collective.xmltestreport=1.0-eea

[xmltestreport]
recipe = collective.xmltestreport
eggs =
    ${instance:eggs}
extra-paths =
    ${zope2:location}/lib/python
zope-conf =
    ${instance:location}/etc/zope.conf

defaults = ['--exit-with-status', '--no-warning', '--xml']

Changelog