Changes between Version 78 and Version 79 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 22, 2009, 1:04:45 AM (10 years ago)
Author:
GlennHumphrey
Comment:

/* Measuring Progress */ Simple word change

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v78 v79  
    8888
    8989
    90 As mentioned above, the ''covmerge'' script produces reports that contain several metrics that can be 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 these metrics provide useful information about the status or progress of the Object Code Coverage.
     90As mentioned above, the ''covmerge'' program produces reports that contain several metrics that can be 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 these metrics provide useful information about the status or progress of the Object Code Coverage.
    9191
    9292When we started the RTEMS Code Coverage effort, we did not immediately capture results to measure progress.  This actually ended up being the correct thing to do since the ''covmerge'' tool was in development and often produced results that were not directly comparable.  Now that the development of ''covmerge'' has largely settled, we can perform coverage runs on several RTEMS release points and see the progress of the coverage effort.  The results shown below were of the POSIX Enabled Profile run on the SPARC/ERC32.