Changes between Version 24 and Version 25 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 8, 2009, 11:47:51 PM (10 years ago)
Author:
JoelSherrill
Comment:

/* Coverage Profiles */ Rename profiles, enhance text

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v24 v25  
    7979
    8080RTEMS 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.
    81 = Classic and POSIX =
     81
     82As 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.
     83= POSIX Enabled =
    8284
    8385
    84 This is the first profile we tested. This focused on the score, sapi, rtems, and posix directories in the cpukit directory.  This profile represents a full tasking and synchronization feature set.
    85 = Classic Only =
     86This is the first profile we tested. This initially focused on the score, sapi, rtems, and posix directories in the cpukit directory.  This profile represents a full tasking and synchronization feature set. 
     87= Classic API Only (POSIX Disabled) =
    8688
    8789
     
    9092 *  features in score only exercised by POSIX
    9193 *  features in score available via Classic API but only tested via POSIX
    92  *  POSIX features like sleep() which are enabled with POSIX threads are disabled.
     94 *  POSIX features like sleep() which are enabled when POSIX threads are disabled.
    9395
    9496The first case will allow us to disable score features in this configuration and reduce the code size.
    9597
    9698The second case allows us to approach 100% coverage in every RTEMS configuration.
    97 = Classic, POSIX, and Other CPUKit Components (experimental) =
     99
     100The third case is similar to the second and indicates the need for tests in this configuration for features that are technically part of the POSIX API support.
     101= Developmental =
    98102
    99103