Changes between Version 41 and Version 42 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 16, 2009, 7:30:26 PM (10 years ago)
Author:
GlennHumphrey
Comment:

/* What was Discovered */ Added a paragraph about observations

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v41 v42  
    5656
    5757
    58 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.
     58As 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 about the status or progress of the Object Code Coverage.
     59
     60When we began the RTEMS Code Coverage effort, we performed coverage analysis on the developmental head of RTEMS 4.6 using the POSIX Enabled Profile.  Some of our initial observations were interesting.  First, we were a little surprised at the incompleteness of the test suite.  We knew that there were some areas of the RTEMS code that were not tested at all, but we also found that areas we thought were tested were only partially tested.  Another surprise was that coding habits and style generated a lot of unreachable object code.
    5961= Resolving Uncovered Code =
    6062