Updated Jenkins to use pytest

Author: mikej888

jenkins/Languages.md

@@ -1,7 +1,7 @@
 Create a Jenkins job for popular programming languages
 ======================================================
 
-Jenkins can build and run code written in many languages, including C, C++, Fortran, Java, PHP and Python code, either directly or via automated build tools like Make or ANT. It can also run unit tests, for example written in CUnit, CppUnit, googletest, FRUIT, JUnit, PHPUnit or nosetests, and report on the success or failure of tests.
+Jenkins can build and run code written in many languages, including C, C++, Fortran, Java, PHP and Python code, either directly or via automated build tools like Make or ANT. It can also run unit tests, for example written for CUnit, CppUnit, googletest, FRUIT, JUnit, PHPUnit or pytest, and report on the success or failure of tests.
 
 Create a Jenkins job
 --------------------
@@ -67,7 +67,7 @@ phpunit --log-junit TestResults.xml --bootstrap src/autoload.php test/FibonacciT
 * Python
 
 ```
-nosetests --with-xunit
+py.test --junit-xml=report.xml
 ```
 
 For Java, Jenkins has in-built support for ANT:
@@ -96,7 +96,7 @@ For all languages:
 Publish test results
 --------------------
 
-Jenkins can parse XML test results, in JUnit-compliant XML results file, and present test in a more useful, interactive way, that allows the test packages, classes, modules, classes, methods and functions to be browsed. Many test frameworks either output JUnit-compliant XML directly (e.g. googletest, FRUIT, JUnit, PHPUnit and nosetests) or in an XML format that can be converted into a JUnit-compliant XML results file (e.g. CUnit - our `make xunit-report` target does this conversion). CppUnit outputs an XML file, `TestResults.xml`, but this is not in xUnit-compliant XML format and a conversion does not, yet, exist.
+Jenkins can parse XML test results, in JUnit-compliant XML results file, and present test in a more useful, interactive way, that allows the test packages, classes, modules, classes, methods and functions to be browsed. Many test frameworks either output JUnit-compliant XML directly (e.g. googletest, FRUIT, JUnit, PHPUnit and pytest) or in an XML format that can be converted into a JUnit-compliant XML results file (e.g. CUnit - our `make xunit-report` target does this conversion). CppUnit outputs an XML file, `TestResults.xml`, but this is not in xUnit-compliant XML format and a conversion does not, yet, exist.
 
 To instruct Jenkins to parse these result files
 
@@ -110,7 +110,7 @@ To instruct Jenkins to parse these result files
   - Fortran: `result.xml`
   - Java: `build/test/xml/TESTS-TestSuites.xml`
   - PHP: `TestResults.xml`
-  - Python:  `nosetests.xml`
+  - Python:  `report.xml`
 * If you get a warning that your file `doesn't match anything` you can ignore this as the file hasn't been created yet.
 * Click Save.
 * Click Build Now.
@@ -139,7 +139,7 @@ How Jenkins behaves when there are errors
 
 * This time the ball in the Build History table should be one of yellow or red.
   - C, Fortran and Java will show as yellow.  Yellow means the build is unstable. Jenkins [defines](https://wiki.jenkins-ci.org/display/JENKINS/Terminology) a build as unstable if it was built successfully but a test result publisher has noted that a test has failed. This is because CUnit, FRUIT, and JUnit (invoked via ANT's `junit` task) returns an exit code of `0`, indicating success, Jenkins executes the post-build action to parse the test results file and so detects the test failures.
-  - C++, PHP and Python will show as red. This means the build failed. This is because googletest, PHPUnit and nosetests return an exit code of `1` if any test fails. 
+  - C++, PHP and Python will show as red. This means the build failed. This is because googletest, PHPUnit and pytest return an exit code of `1` if any test fails. 
 * Click the job link.
 * Click the Test Result link and you can browse to see the individual test functions that failed. Remember, too that the console output is always available via the Console Output link.
 * Click Back to project then Back to dashboard.

jenkins/README.md

@@ -15,7 +15,7 @@ Install and deploy Jenkins
 Use Jenkins to run build-and-test jobs for various languages
 ------------------------------------------------------------
 
-Jenkins can build and run code written in many languages, including C, C++, Fortran, Java, PHP and Python code, either directly or via automated build tools like Make or ANT. It can also run unit tests, for example written in CUnit, CppUnit, googletest, FRUIT, JUnit, PHPUnit or nosetests, and report on the success or failure of tests.
+Jenkins can build and run code written in many languages, including C, C++, Fortran, Java, PHP and Python code, either directly or via automated build tools like Make or ANT. It can also run unit tests, for example written for CUnit, CppUnit, googletest, FRUIT, JUnit, PHPUnit or pytest, and report on the success or failure of tests.
 
 * [Create a Jenkins job for popular programming languages](./Languages.md) including C, C++, Fortran, Java, PHP and Python.
 

jenkins/VersionControl.md

@@ -15,7 +15,7 @@ Run:
 ```
 $ cp -r build_and_test_examples/python python-git
 $ cd python-git
-$ rm -f nosetests.xml *.pyc */*.pyc .gitignore 
+$ rm -rf report.xml maths/*.pyc maths/tests/*.pyc maths/tests/__pycache__ .gitignore 
 $ git init
 $ git config --global user.name "Your name"
 $ git config --global user.email [email protected]
@@ -26,7 +26,7 @@ $ git commit -m "Initial import" .
 Remove the current working files and set this repository to be a "bare" repository i.e. one with no current working copy:
 
 ```
-$ rm -rf __init__.py src/ README.md  test/ xxx.md 
+$ rm -rf README.md maths
 $ git config --bool core.bare true
 ```
 
@@ -44,7 +44,7 @@ Run:
 ```
 $ cp -r build_and_test_examples/python python-mercurial
 $ cd python-mercurial
-$ rm -f nosetests.xml *.pyc */*.pyc .gitignore 
+$ rm -rf report.xml maths/*.pyc maths/tests/*.pyc maths/tests/__pycache__ .gitignore 
 $ hg init
 $ hg add .
 $ hg commit -m "Initial import" .
@@ -58,7 +58,7 @@ Run:
 $ svnadmin create $HOME/SVNROOT
 $ cp -r build_and_test_examples/python python
 $ cd python/
-$ rm -f nosetests.xml *.pyc */*.pyc .gitignore 
+$ rm -rf report.xml maths/*.pyc maths/tests/*.pyc maths/tests/__pycache__ .gitignore 
 $ svn import file://$HOME/SVNROOT/python -m "Initial import"
 ```
 
@@ -70,7 +70,7 @@ Run:
 $ cvs -d $HOME/CVSROOT init
 $ cp -r build_and_test_examples/python python
 $ cd python/
-$ rm -f nosetests.xml *.pyc */*.pyc .gitignore 
+$ rm -rf report.xml maths/*.pyc maths/tests/*.pyc maths/tests/__pycache__ .gitignore 
 $ cvs -d $HOME/CVSROOT import -m "Initial import" python vendor-tag release-tag
 ```
 
@@ -122,15 +122,15 @@ Check out the repository and runs tests
   - Modules Remote Name: `python`
 * Scroll down the page to under the Build heading.
 * Click Add build step and select Execute shell.
-* Enter the commands that run the tests using nosetests:
+* Enter the commands that run the tests using `py.test`:
 
 ```
-nosetests --with-xunit
+py.test --junit-xml=report.xml
 ```
 
 * Under the Post-build Actions heading, click Add post-build action.
 * Select Publish JUnit test result report.
-* In the Test report XMLs field enter the location of the test report XML file, `nosetests.xml`.
+* In the Test report XMLs field enter the location of the test report XML file, `report.xml`.
 * Click Save.
 * Click Build Now.
 * When the job completes, click on the job's link in the Build History table.

jenkins/examples/CVS job/config.xml

@@ -52,12 +52,12 @@
   <concurrentBuild>false</concurrentBuild>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>

jenkins/examples/Git job/config.xml

@@ -33,12 +33,12 @@
   <concurrentBuild>false</concurrentBuild>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>

jenkins/examples/Mercurial job/config.xml

@@ -26,13 +26,12 @@
   <concurrentBuild>false</concurrentBuild>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit
-</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>

jenkins/examples/Periodic job/config.xml

@@ -18,16 +18,16 @@
   <customWorkspace>$HOME/build_and_test_examples/python</customWorkspace>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>
     </hudson.tasks.junit.JUnitResultArchiver>
   </publishers>
   <buildWrappers/>
-</project>
+</project>

jenkins/examples/Python job/config.xml

@@ -14,16 +14,16 @@
   <customWorkspace>$HOME/build_and_test_examples/python</customWorkspace>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>
     </hudson.tasks.junit.JUnitResultArchiver>
   </publishers>
   <buildWrappers/>
-</project>
+</project>

jenkins/examples/SVN job/config.xml

@@ -35,12 +35,12 @@
   <concurrentBuild>false</concurrentBuild>
   <builders>
     <hudson.tasks.Shell>
-      <command>nosetests --with-xunit</command>
+      <command>py.test --junit-xml=report.xml</command>
     </hudson.tasks.Shell>
   </builders>
   <publishers>
     <hudson.tasks.junit.JUnitResultArchiver plugin="[email protected]">
-      <testResults>nosetests.xml</testResults>
+      <testResults>report.xml</testResults>
       <keepLongStdio>false</keepLongStdio>
       <testDataPublishers/>
       <healthScaleFactor>1.0</healthScaleFactor>