|
I have integration tests implemented in JavaScript which run automatically on an embedded system post build. Currently Jenkins kicks off the image build, deploys it to the device, and ssh into the device to validate basic success/fail. The device has an embedded browser which has API hooks I need to test, I have created a bunch of tests implemented in JavaScript that run within the browser. Currently the tests just produces output displaying the results of the tests in XML. I'd like to tie the results of the tests back into Jenkins if possible and wondering what the easiest way of going about this would be. So far the options I have thought of thus far are:
Any other thoughts? Any plugins I could leverage for this? The challenge here is that my tests run on the device within the embedded browser (JavaScript, HTML4 domapi) 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. Mark Waite
|
|
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. https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin 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, Mgimza On Wed, Oct 10, 2012 at 4:08 PM, tiburblium <[hidden email]> wrote:
|
| Powered by Nabble | Edit this page |
