Changes between Version 35 and Version 36 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 15, 2009, 11:42:22 PM (10 years ago)
Author:
GlennHumphrey
Comment:

Added a table of files produced by covmerge

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v35 v36  
    2828
    2929One issue that had to be addressed was the different coverage map formats.  Each source of a coverage map (e.g. simulator, hardware debugger, etc.) may produce a coverage map in a different format.  The ''covmerge'' tool is implemented using C++ classes and provides for inheriting new Coverage Reader and Writer classes for specific coverage map formats.  This allows different formats to be converted to the basic format used by ''covmerge''.  The ''covmerge'' script currently supports the formats produced by the TSIM and Skyeye simulators.
     30
     31The output produced by covmerge is actually a set of simple ASCII files that give a developer the necessary information to quickly determine the current status of the Code Coverage and enough information to determine the location of the uncovered code.  The following set of files is produced by covmerge.
     32
     33{| border="1" style="margin: 1em auto 1em auto;text-align: left;"
     34|+
     35|-
     36|'''file name''' || '''purpose of file'''
     37|-
     38| A || if (x OR y)
     39|-
     40| B || do something
     41|-
     42|}
     43
    3044<br style="clear: both" />
    3145= What was Discovered =
    3246
    3347
    34 As mentioned above, the covmerge script produces reports that contain several metrics used to measure progress.  The first is the number of uncovered object code ranges.  The second is the percent of untested object code as a percentage of the total object code size under analysis.  Together the metrics provide useful information.  Some uncovered ranges may be a single instruction so eliminating that case improves the first metric more than the second.
     48As mentioned above, the ''covmerge'' script produces reports that contain several metrics used to measure progress.  The first is the number of uncovered object code ranges.  The second is the percent of untested object code as a percentage of the total object code size under analysis.  Together the metrics provide useful information.  Some uncovered ranges may be a single instruction so eliminating that case improves the first metric more than the second.
    3549= Resolving Uncovered Code =
    3650