Include test summary in build notifications

[randomsync]

Include test summary in build notification. A checkbox is added to build settings page which can be used to specify whether to include test summary or not. If enabled and no tests are found, a "No Tests found" message is appended.

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

[samrocketman]

I guess I'll start maintaining this plugin. I don't have any experience developing Jenkins plugins but if I can get my own environment set up and learn to release then I'll do it. This may take about a week.

[samrocketman]

Candidate for merge means I will first merge your change locally, compile locally, and test locally in Jenkins before merging.

[samrocketman]

@randomsync I can't seem to be able to produce output from the build. I didn't have an issue with the merge conflicts.

Can you perhaps explain to me how to publish test results in a Job in order to make this feature execute? So far I've tried Publish JUnit test report but I can't seem to get a summary out of it.

[samrocketman]

Never mind haha, I didn't have the checkbox to publish results checked in the job configuration.

[randomsync]

Thanks @samrocketman

[samrocketman]

You're welcome.

[samrocketman]

I'll be moving include test summary into the advanced section (it will be at the bottom). That's where you'll find your setting in the next release.

[johnjohndoe]

Could you please tell me if Jenkins ver. 1.651.3 is capable of producing a summary for JUnit tests as shown on the screenshot in the first post of this issue?
I would like to send them to Slack using the Slack plugin.

[fastsieg]

I'm using rspec for my Ruby project, so I get a no Test found message. It would be nice if one could choose what kind of tests are beeing done.
What also could be a problem is that I run my tests inside a docker container. I don't know if the test results are accessable to the plugin then.

[samrocketman]

fastsieg, that's more a limitation in Jenkins than this plugin. JUnit-style tests are what Jenkins collects. If you run your tests inside of a container then perhaps you should use docker to retrieve the results (or specify a volume if docker is running on the same machine as the Jenkins agent).

[randomsync]

@fastsieg also, you can add rspec_junit_formatter to your Gemfile to produce the junit style report.

[remeltucker]

Using xcpretty to parse the output from xcodebuild as Junit.The test results analyser plugin works fine since it depends on the junit results but the test summary and custom message for slack is not getting posted. Any thoughts ?

[dhiltonp]

For the result summary to work, you need to have a compatible xml file, which is then fed into the Post-build action of "Publish JUnit test result report".

Once that's working, the jenkins slack bot will have access to the test results to provide a summary.

[johnjohndoe]

Where can I find out about how the "compatible xml file" has to look like and how to generate it?

[samrocketman]

Web search junit xml. e.g. http://stackoverflow.com/questions/4922867/junit-xml-format-specification-that-hudson-supports

[johnjohndoe]

For my understanding: this manual configuration file is only needed with Jenkins 1.6? The current version of Jenkins automatically outputs test summaries?

[samrocketman]

Not sure what you mean. It's just JUnit. As far as I know, without additional plugins the test summary comes from JUnit. That is not specific to a particular version of Jenkins.

[johnjohndoe]

Finally, I found out that the path to look for Test report XMLs must be entered in the Publish JUnit test result report action as shown in the screenshot. For my Android project which comes with multiple Gradle product flavors the following path works:

**/build/test-results/**/TEST-*.xml

[Prasannajnaeyulu]

For the result summary to work, you need to have a compatible xml file, which is then fed into the Post-build action of "Publish JUnit test result report".

Once that's working, the jenkins slack bot will have access to the test results to provide a summary.

This is shown as an example in the previous comment

[bitsydarel]

How to publish junit report in jenkins declarative pipeline ?

[bitsydarel]

or where to find the include test summary checkbox...

[swanandvg]

@bitsydarel
You have to cd to directory where result.xml is stored and then use-
junit "*.xml"

if xml file is new one, then only it will publish result to Jenkins. If result is not new, and still if you want to publish results, modify last modified datetime for xmls-

script {
def testResults = findFiles(glob: '*.xml')
for(xml in testResults) {
touch xml.getPath()
}
}