Changes between Version 62 and Version 63 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 18, 2009, 7:54:42 PM (10 years ago)
Author:
GlennHumphrey
Comment:

/* Coverage Profiles */ Began definition of the two groups that make up profiles

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v62 v63  
    112112
    113113
    114 RTEMS includes a lot of source code and the coverage analysis should focus on improving the test coverage of well-defined code subsets with a trend over time of increasing both the level of coverage (e.g. object to statement to decision to MC/DC) and the amount of source code covered.
     114RTEMS contains a lot of source code and although the primary focus of coverage analysis is to achieve 100% coverage of well-defined code subsets, we would also like to increase the amount of source code analyzed.  In order to manage the increase in a controlled manner, we defined to basic groups of source code.  The first group is called Baseline and the second group is called Developmental.  The Baseline group contains the source code that has achieved (or nearly achieved) 100% Object Code Coverage.  The Developmental group contains the source code for which there are very few test cases and therefore very poor coverage.
     115
     116Initially, the Baseline group included the source code from the following directories:  XXX and YYY.
    115117
    116118As other support libraries in cpukit is covered, these will be move from the Developmental Profile and added to the '''POSIX Enabled''' and '''Classic API Only''' profiles