Reporting Jumi test as JUnit XML

[Bruno Bieth]

I'd like to integrate Jumi with Jenkins. Jenkins has the ability to parse JUnit XML reports and nicely print them on the web console.

Is it possible to format Jumi test results in JUnit XML?

Thanks

[Esko Luontola]

Not yet, but it's in the roadmap. [1]

I'm currenty working on reusing the Jumi test runner daemon process for
multiple test suite executions, so that the tests can be ran much
faster. [2] Then I'll implement support for ignored tests (i.e. JUnit's
@Ignore and assumeThat), but after that the new features can be
prioritized quite freely.

If Jenkins integration is important for you, I can push JUnit XML
support higher in Jumi's backlog. What benefits are you especially
interested in getting by using Jumi with Jenkins?

[1] https://github.com/orfjackal/jumi/blob/master/ROADMAP.txt
[2] http://blog.orfjackal.net/2013/02/faster-junit-tests-with-jumi-test.html

--
Esko Luontola
www.orfjackal.net

[Bruno Bieth]

If Jenkins integration is important for you, I can push JUnit XML
support higher in Jumi's backlog. What benefits are you especially
interested in getting by using Jumi with Jenkins?

Well I'm sure you know the benefits of CI. I'm using Jenkins. Jenkins has this convenient feature that shows you failed tests without having to dive into the build console output.

For that you need your tests results encoded in the JUnit XML format.

[Esko Luontola]

Bruno Bieth wrote on 4.11.2013 11:21:
> Well I'm sure you know the benefits of CI. I'm using Jenkins. Jenkins
> has this convenient feature that shows you failed tests without having
> to dive into the build console output.
> For that you need your tests results encoded in the JUnit XML format.

Yes. The reason why I'm asking is that currently the only testing
framework that runs only on Jumi is http://specsy.org/ - a testing
framework that I wrote. When using only JUnit tests, it's possible to
run them using JUnit on the CI and use Jumi only while writing code.

It's a kind of a chicken-and-egg problem regarding tool support and
users. Currently I feel that the best way to get more users for Jumi is
to improve its performance [1] so that people would get faster feedback
while writing code, even though the CI would not get those benefits.

[1] http://blog.orfjackal.net/2013/02/faster-junit-tests-with-jumi-test.html

--
Esko Luontola
www.orfjackal.net