Generating Kyua test result output in JUnit XML format for Jenkins integration?

[Julio Merino]

On Mon, Feb 24, 2014 at 4:11 PM, Craig Rodrigues <rodrigc at freebsd.org> wrote:
>
> Hi,
> How hard would it be to add some code
> to Kyua to optionally be able to generate test result output
> in JUnit XML?

(For changes to Kyua itself, please don't forget to include the
kyua-discuss (at googlegroups.com) mailing list.)

> It would be super cool if by BSDCan we could demo:

Certainly. I should have some decent amount of time in a couple of
weeks to work on this. Improving reports is the highest priority thing
that I have to focus on to improve the face of the test suite.

> How hard would this be to do?
>
>
> Is there anyone available who is interested in working on this?

It's not hard: the report generation code is self-contained as you can
see in cmd_report.cpp and cmd_report_html.cpp. And I think adding
JUnit XML output would be a nice addition.

In the mid-to-long term, I have some ideas on how to redo the whole
report generation code to make it easier to extend and customize.
(Well, basically just some ideas I wanna toy with -- which involve
rewriting this whole thing in Lua so that adding new backends can be
done without rebuilding Kyua.) But these changes will take some time.

A first strategical step separate from that and that would make your
proposal simpler is to remove the special-cased report-html and
instead make the "report" command be able to spit out various formats
based on a flag (e.g. --output=junit:/my/file.xml,
--output=html:/my/file.html). I have to do this anyway to resolve some
"show-stopper" issues in NetBSD land, and with this done plugging a
JUnit backend would be trivial and mostly a copy/paste of the HTML
backend.