Good morning,
It seems that the results.xml file format is not the same one as JUnit or TestNG, so Jenkins isn't able to display ABLUnit result trends. Would it be possible to change the file format so that Jenkins could directly display the results ? Or tell if this is another common file format ?
Gilles
I asked or the same XML output as well.
Our own unit testing tool does that. And that's really one of the most important bits for tool interoperability!
+100 on interoperability. If I have to develop a custom plugin for Jenkins and any other continuous integration tool on the market, that's a showstopper for me.
As it is XML can we not just get a XSLT to transform the XML from ABLUnit standard to other standards? This should be easy enough as you are just formatting XML from one layout to another? And will mean we could do a lot more with it.
But why not use "THE" defacto standard right from the begining?
even if the xml can't be changed , surely you don't need to write a
plugin for jenkins, just a 4gl class to read the xml in, and convert
it to the standard xml ... even json ;)
On 31 January 2014 11:02, Riverside Software
wrote:
> RE: ABLUnit - Results.xml file format
> Reply by Riverside Software
>
> +100 on interoperability. If I have to develop a custom plugin for Jenkins
> and any other continuous integration tool on the market, that's a
> showstopper for me.
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Julian Lyndon-Smith
IT Director,
dot.r
http://www.dotr.com
"The bitterness of poor quality remains long after the sweetness of
low price is forgotten"
Follow dot.r on http://twitter.com/DotRlimited
Sure Julian, XML's can be transformed, regenerated and all other funny stuff be done.
But why invent a new format? Just because you can?
Or is there information in that XML that does not fit into the JUnit one?
you do have a point ... we're agreeing yet again ...
On 31 January 2014 11:15, Mike Fechner
wrote:
> RE: ABLUnit - Results.xml file format
> Reply by Mike Fechner
>
> But why not use "THE" defacto standard right from the begining?
>
> Stop receiving emails on this subject.
>
> Flag this post as spam/abuse.
--
Julian Lyndon-Smith
IT Director,
dot.r
http://www.dotr.com
"The bitterness of poor quality remains long after the sweetness of
low price is forgotten"
Follow dot.r on http://twitter.com/DotRlimited
Good morning,
It seems that the results.xml file format is not the same one as JUnit or TestNG, so Jenkins isn't able to display ABLUnit result trends. Would it be possible to change the file format so that Jenkins could directly display the results ? Or tell if this is another common file format ?
Gilles
Flag this post as spam/abuse.
I'm with Mike on this one. If there's a standard for Unit testing XMLs then use it. OR, if yours is truly better, explain why so we see the benefit, and provide the standard as an option anyway... :)
FWIW I've uploaded our code that works with JUnit XML (based on SAX-WRITER) to dropbox. There's also an XSD and a sample I found when I was looking for one.
Just an update on this question, mainly for your information and comment.
We've changed the format of the results XML files to follow the Jenkins JUnit XSD Schema . The results files can now be viewed in the Eclipse JUnit views and also in Jenkins. I wanted to let you know and also make sure that this addresses your previous concerns and covers the use-cases.
Regards,
-- peter