unittest-based test runner with Ant/JUnit like XML reporting.
unittest-xml-reporting (aka xmlrunner)
A unittest test runner that can save test results to XML files in xUnit format. The files can be consumed by a wide range of tools, such as build systems, IDEs and continuous integration servers.
There are many schemas with minor differences.
We use one that is compatible with Jenkins xUnit plugin, a copy is
tests/vendor/jenkins/xunit-plugin/junit-10.xsd (see attached license).
- Jenkins (junit-10.xsd), xunit plugin (2014-2018), please note the latest versions (2.2.4 and above are not backwards compatible)
You may also find these resources useful:
- Jenkins (junit-10.xsd), xunit plugin 2.2.4+
- JUnit-Schema (JUnit.xsd)
- Windyroad (JUnit.xsd)
- a gist (Jenkins xUnit test result schema)
Things that are somewhat broken
Python 3 has the concept of sub-tests for a
unittest.TestCase; this doesn't map well to an existing
xUnit concept, so you won't find it in the schema. What that means, is that you lose some granularity
in the reports for sub-tests.
- Python 2.7 or 3.3+
- Please note Python 2.6 end-of-life was in Oct 2013, last version supporting 2.6 was 1.14.0
The easiest way to install unittest-xml-reporting is via Pip:
$ pip install unittest-xml-reporting
If you use Git and want to get the latest development version:
$ git clone https://github.com/xmlrunner/unittest-xml-reporting.git $ cd unittest-xml-reporting $ sudo python setup.py install
Or get the latest development version as a tarball:
$ wget https://github.com/xmlrunner/unittest-xml-reporting/archive/master.zip $ unzip master.zip $ cd unittest-xml-reporting $ sudo python setup.py install
Or you can manually download the latest released version from PyPI.
python -m xmlrunner [options] python -m xmlrunner discover [options] # help python -m xmlrunner -h
python -m xmlrunner discover -t ~/mycode/tests -o /tmp/build/junit-reports
The script below, adapted from the
unittest, shows how to use
XMLTestRunner in a very simple way. In fact, the only difference between
this script and the original one is the last line:
import random import unittest import xmlrunner class TestSequenceFunctions(unittest.TestCase): def setUp(self): self.seq = list(range(10)) @unittest.skip("demonstrating skipping") def test_skipped(self): self.fail("shouldn't happen") def test_shuffle(self): # make sure the shuffled sequence does not lose any elements random.shuffle(self.seq) self.seq.sort() self.assertEqual(self.seq, list(range(10))) # should raise an exception for an immutable sequence self.assertRaises(TypeError, random.shuffle, (1,2,3)) def test_choice(self): element = random.choice(self.seq) self.assertTrue(element in self.seq) def test_sample(self): with self.assertRaises(ValueError): random.sample(self.seq, 20) for element in random.sample(self.seq, 5): self.assertTrue(element in self.seq) if __name__ == '__main__': unittest.main( testRunner=xmlrunner.XMLTestRunner(output='test-reports'), # these make sure that some options that are not applicable # remain hidden from the help menu. failfast=False, buffer=False, catchbreak=False)
Reporting to a single file
if __name__ == '__main__': with open('/path/to/results.xml', 'wb') as output: unittest.main( testRunner=xmlrunner.XMLTestRunner(output=output), failfast=False, buffer=False, catchbreak=False)
The XMLTestRunner can also be used to report on docstrings style tests.
import doctest import xmlrunner def twice(n): """ >>> twice(5) 10 """ return 2 * n class Multiplicator(object): def threetimes(self, n): """ >>> Multiplicator().threetimes(5) 15 """ return 3 * n if __name__ == "__main__": suite = doctest.DocTestSuite() xmlrunner.XMLTestRunner().run(suite)
In order to plug
XMLTestRunner to a Django project, add the following
TEST_RUNNER = 'xmlrunner.extra.djangotestrunner.XMLTestRunner'
Also, the following settings are provided so you can fine tune the reports:
||Besides the XML reports generated by the test runner, a bunch of useful information is printed to the
||If your test methods contains docstrings, you can display such docstrings instead of display the test name (ex:
In order to use this feature, you have to enable verbose output by setting
Only effects stdout and not XML output.
||Tells the test runner where to put the XML reports. If the directory couldn't be found, the test runner will try to create it before generate the XML files.|
||Tells the test runner to output a single XML report with this filename under
Please note that for long running tests, this will keep the results in memory for a longer time than multiple reports, and may use up more resources.
We are always looking for good contributions, so please just fork the repository and send pull requests (with tests!).
If you would like write access to the repository, or become a maintainer, feel free to get in touch.
Testing changes with
tox to test your changes before sending a pull request.
You can find more information about
tox at https://testrun.org/tox/latest/.
$ pip install tox # basic sanity test, friendly output $ tox -e pytest # all combinations $ tox
Release history Release notifications
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size unittest_xml_reporting-2.5.2-py2.py3-none-any.whl (19.2 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View hashes|
|Filename, size unittest-xml-reporting-2.5.2.tar.gz (16.4 kB)||File type Source||Python version None||Upload date||Hashes View hashes|
Hashes for unittest_xml_reporting-2.5.2-py2.py3-none-any.whl
Hashes for unittest-xml-reporting-2.5.2.tar.gz