[RTEMS Project] #2261: Add coverage report generation support to rtems-tools

[RTEMS trac]

#2261: Add coverage report generation support to rtems-tools
---------------------------+-------------------
 Reporter:  joel.sherrill  |       Owner:
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  General        |     Version:  4.11
 Severity:  normal         |  Resolution:
 Keywords:                 |
---------------------------+-------------------
Description changed by joel.sherrill:

Old description:

> This ticket is to capture the current state of the project started by
> Krzysztof Mięsowicz <krzysztof.miesowicz at gmail.com>. The remaining effort
> in conjunction with other activity related to coverage such as inclusion
> of gcov generated reports is a good "summer of code" type project. This
> is an important capability to add to the rtems-tools.
>
> The attached tar file krzy-patches.tar.bz2 contains the current code.
> There may be other issues to resolve but writing from memory, the
> following are the highest priority ones:
>
> * no default setting for coverage enable/disable
> * configuration file has hard coded paths. This should be able to be a
> template which is adjusted by the tools at run-time.
> * variable naming and coding style does not match that used in other
> Python code in rtems-tools
>
> Krzysztof wrote some in his blog about this
> (http://kmiesowicz.blogspot.com/p/esa-socis-2014.html). Ensure that your
> base RTEMS tools are built with the RTEMS Source Builder and check on the
> development list if it builds a qemu with coverage support. This may have
> changed since he blogged.

New description:

 This ticket is to capture the current state of the project started by
 Krzysztof Mięsowicz <krzysztof.miesowicz at gmail.com>. The goals of the
 project were to:

 * replace the existing shell scripts in rtems-testing with Python code
 integrated into rtems-tools
 * add the capability to generate a report per directory. This is important
 because a large body of code with low coverage negatively impacts the
 overall coverage area and makes reports harder to read. Breaking the
 reports down by functional area lets us do coverage reporting on more code
 even when some of the areas are in need of testing improvement.

 The remaining effort in conjunction with other activity related to
 coverage such as inclusion of gcov generated reports is a good "summer of
 code" type project. This is an important capability to add to the rtems-
 tools.

 The attached tar file krzy-patches.tar.bz2 contains the current code.
 There may be other issues to resolve but writing from memory, the
 following are the highest priority ones:

 * no default setting for coverage enable/disable
 * configuration file has hard coded paths. This should be able to be a
 template which is adjusted by the tools at run-time.
 * variable naming and coding style does not match that used in other
 Python code in rtems-tools

 Krzysztof wrote some in his blog about this
 (http://kmiesowicz.blogspot.com/p/esa-socis-2014.html). Ensure that your
 base RTEMS tools are built with the RTEMS Source Builder and check on the
 development list if it builds a qemu with coverage support. This may have
 changed since he blogged.

--

--
Ticket URL: <http://devel.rtems.org/ticket/2261#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project