[Fuego] Update on recent activity
Tim.Bird at sony.com
Thu Jun 22 23:44:08 UTC 2017
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> I've been working on the third topic (uniform test output) for a bit. So far this
> is what I had been able to achieve:
> - I refactored the parser to produce a single run.json file for each job build.
> This run.json contains both metadata related to the run and the actual
> + I am extending the parser to handle some things such as error messages
> or duration "per testcase".
> - The parser still produces a results.json file that merges the most important
> data in the run.json files for the flot visualizer plugin.
> - I have added support for Junit output. This basically consists of "translating"
> part of the data stored in run.json into the Junit format that
> the Jenkins plugin "Test Results Analyzer"  understands. This plugin is
> quite neat because it displays the results as an HTML table and allows
> generating graphs (which you can download in png/svg format) and more.
> However, it is not as flexible as I wanted so I might leave it as an option
> and fix the custom HTML tables code created by AGL.
> - After studying Junit format and TAP13, I've concluded that a new common
> test output format is required and I have written a first draft. I will be sharing
> once it is ready, I know it works on a variety of tests (both Functional/Unit
> tests and Benchmark tests) and I provide a Jenkins plugin for it.
This sounds great. For the short term (next day or two), I'm working on
getting LTSI testing set up in my personal Fuego "lab". I just got a Minnowboard
turbot from Intel, and installed it today. (Due to what appears to be flakey
microSD cards, it took me 4 attempts to get Ubuntu installed on it - Ugh.)
Renesas is sending me an R-Car board as well.
I'll be happy to look at the uniform output stuff when it's ready.
More information about the Fuego