I'd second this option. It's been a good approach to getting test results out of all sorts of tools. I've written scripts that generated this format from shell scripts and other sources depending on what I was doing and they work great and appear just like any other test results in Jenkins.
Ben On Mon, Mar 11, 2013 at 6:11 PM, JonathanRRogers <[email protected]> wrote: > On Monday, March 11, 2013 8:25:23 AM UTC-4, zakyn wrote: >> >> Hello, >> >> I would like to ask you for your experience about publishing the GUI tests >> or postbuild results. >> >> We have this situation: >> 1. run build >> 2. on the dedeicated machine we run automated gui tests using build >> results >> >> and I would like to add the results of the tests to the build. > > > By "the dedicated machine" do you mean the machine running Jenkins? > >> >> >> My idea is publish it as html page. So after the build there is a link to >> some html page without the tests. And after running the tests this page >> will be rewriten with the results. >> >> Is there anything what could help me please? > > > I use the xUnit Plugin, which unsurprisingly consumes test results in the > Xunit format: > <URL:https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
