Changes between Version 2 and Version 3 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Aug 5, 2009, 11:54:16 PM (10 years ago)
Author:
JoelSherrill
Comment:

Fix text

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v2 v3  
    88RTEMS is used in many critical systems.  It is important that the RTEMS Project ensure that the RTEMS product is tested as thoroughly as possible.  In this light, we want to ensure that as close to 100% of the generate assembly code is executed by the RTEMS test suite.  We perform automated coverage testing using an processor simulator in conjunction with a set of RTEMS specific support scripts.
    99
    10 
    11 
    12 
    13 There are multiple ways to measure progress on this task. In the past, we have used two metrics.  The first is the reduction in the number of uncovered binary code ranges from that identified initially.  The second is the percent of untested binary object code as a percentage of the total 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.
     10There are multiple ways to measure progress on this task. We primarily use two metrics.  The first is the reduction in the number of uncovered binary code ranges from that identified initially.  The second is the percent of untested binary object code as a percentage of the total 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.
    1411= Test Theory =
    1512