Thanks for any ideas
If you can detect when the tests complete on the embedded system, you might be able to copy the XML test results back to Jenkins, transform the XML to JUnit format, and let Jenkins present the results with its standard JUnit presentation. There are a number of systems which write JUnit compatible output, so you might be able to leverage one of those to assist with the transformation from your XML format to JUnit format.
If you "own" the code that writes the test results in XML, you could also consider writing it directly as JUnit format, thus using a defacto standard for test result output and avoiding translation of the XML to JUnit format.
In reply to this post by tiburblium
It may not be efficient, but I am using JELLY scripting to generate the appropriate email reports from tests that have output outside of jenkins.
I use the Jenkins Email Extension plugin for this setup.
I can access most of the build ( and Jenkins) properties inside the Jelly script.
What I do not have though is the test results stored with the Jenkins build.
If you need to store the test results data in the build log, you could try to use the groovy plugin to incorporate groovy scripts as built steps that will parse and print out your test results.
I hope that this helps,
On Wed, Oct 10, 2012 at 4:08 PM, tiburblium <[hidden email]> wrote:
|Powered by Nabble||Edit this page|