Re: [Fuego] UART/USB Connectivity, History Database, Test result format

["Bird, Timothy" <Tim.Bird@sony.com>]

> -----Original Message-----
> From dhinakar k on Tuesday, March 28, 2017 3:26 AM
> Hi,
> 
> I would like to know how the following are handled by Fuego.
> 
> 1.Connectivity to targets which support UART or USB
>    - If Fuego supports it, then how is it done? (e.g. via Perl Serial module?)
>    - How are the Request/Response handled via UART or USB connectivity?

UART connectivity is handled with the 'serial' transport, using a program
called 'serio'.  Support for this is currently in what I'd call 'alpha' format.
It works, for the most part, with a few issues that need to be resolved
before we can call it an official feature.

For USB there are two methods of support (one existing and one intended):
 * network over USB - that is supported today, but the configuration of the
USB networking is left as an exercise for the user
 * ADB - There are patches available to support ADB, but they are not
currently integrated.

> 2.How can we archive job details, execution results etc.? Does Fuego already
> have support for database? If so, which database? (e.g. MySQL?)

Currently, at a local site, job results are saved in XML in the Jenkins build.xml
file.  Fuego saves it's own parallel set of results to a run.json file (when the test
is executed with 'ftc run-test').  This will be changing shortly (likely in the 1.1 release),
to have all tests (including those executed by Jenkins) create a run.json file.

We have not decided on a centralized database yet, although there is prototype
code in the fuego wiki software to manage json files like a database (e.g. supporting filters
and queries and table generation).  However, this wiki code is not finished yet,
and is lower priority.
 
> 3.What format(s) supported for test results? (json, xunit, yaml, TAP?)
>    All tests integrated into Fuego will output results in the above format?

The target is json, with converters to other formats as needed.  Currently,
benchmarks produce json output, and there is prototype code to have
functional tests produce json output (for sub-tests) as well. The AGL group has code
to produce XML, but it appears they are interested in switching to json output,
and the intent is to unify around this format.

The intent is to have all tests integrated into Fuego produce the json output,
and have report generators that take the format as input.  We have report generators
that take the benchmark data, and functional data (in json) and produce pdf
reports (with xml and tex as intermediate formats).  However, with a big refactoring
that we're doing in the format output, there will be some churn on this part of
Fuego over the next 2 months or so.

> Please answer the above queries.

I hope this is helpful.
 -- Tim