For future reference, the short answer is "yes". The long answer is that failsafe-reports are picked up automatically when the "verify" is the main maven goal of the build (this is a Jenkins Maven Project, not a freestyle one). As I was only running verify in the "post-steps" of the project, it wasn't being picked by Jenkins.
Miguel Almeida On Wed, Mar 14, 2012 at 12:17 PM, Miguel Almeida <[email protected]>wrote: > I have a multi-module maven project running in Jenkins. > > My build #508 had 1,476 tests (number shown in > jenkins/job/Project/508/testReport/). > > Because the tests were running slow, I decided to set the slower tests > into integration tests. With the failsafe plugin, I changed a few classes > from *Test to *IT. The result is that the surefire:report (or test) goal is > much faster. > > Running " mvn clean verify site" locally runs all tests and produces two > surefire reports: surefire-report-unit.html and > surefire-report-integration.html (the file names are the result of my > surefire configuration [1]). > > In Jenkins I still want to see if everything is alright, so I changed the > goal run from "cobertura:cobertura -s $MY_SETTINGS" to "verify > cobertura:cobertura -s $MY_SETTINGS". > > However, the next job shows a* huge decrease in the number of tests*: > jenkins/job/Project512/testReport/ -->409 tests > > My question is: *shouldn't the failsafe tests be reported here as well? *Why > is the testReport not showing the integration tests? > > > I thank you in advance for your help, > > Miguel Almeida > > >
