Issue 47 in xspec: Stylesheet with conversion to JUnit report format will make it more useful for integration into CI servers like Jenkins

[xs...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 47 by fou...@gmail.com: Stylesheet with conversion to JUnit
report format will make it more useful for integration into CI servers like
Jenkins
http://code.google.com/p/xspec/issues/detail?id=47

It would be nice to have a style sheet that converts the results to a JUnit
report format. (I could not find a description of the current report
format, otherwise I'd have done it myself.)

Thanks!

[xs...@googlecode.com]

Updates:
Owner: fgeor...@gmail.com

Comment #1 on issue 47 by fgeor...@gmail.com: Stylesheet with conversion to

JUnit report format will make it more useful for integration into CI
servers like Jenkins
http://code.google.com/p/xspec/issues/detail?id=47

The overall structure of the XML report is similar to the overall
structure of the test suite itself, except the root element is named
x:report. The elements x:scenario, x:label, x:call and x:context are
copied over. The attribute label is normalized to an element x:label.
After a x:call or a x:context, a new element x:result is inserted,
with the value returned by the function or template. Then for each
element x:except in the suite, we have in the report an element x:test
with: an xs:boolean attribute named successful, an element x:label,
and an element x:except with the value actually expected.

Of course, a schema would be better, but I hope this description
might already be enough for you to start.

Let us know your progress... Thank you!