-
Notifications
You must be signed in to change notification settings - Fork 0
Ben O'Steen edited this page Sep 19, 2011
·
1 revision
By using the age-old tactic of 'whichever is the best to understand and use in the fastest time', Jenkins (a fork of Hudson) won out over Build-bot due to its clear configuration and maintenance options. The wealth of plugins available was also a strong factor in its choice.
- Configuring Jenkins with your project
- Using 'tox' with Jenkins | http://readthedocs.org/docs/tox/en/latest/example/jenkins.html
As we are all aiming to use a continuous integration system, it is important that the tool which runs the tests outputs its report in a form that the continuous integration server can interpret.
Jenkins expects the test report to be in a JUnit XML schema. Certain tools can provide this as an output from running a python testsuite:
- 'nosetests TEST_ITEMS --with-xunit' - the XML report will be in './nosetests.xml' by default
- If not using nosetests, you can use the junitxml test runner as demonstrated by Michael Foord