Changes between Version 8 and Version 9 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Aug 18, 2009, 4:02:40 AM (10 years ago)
Author:
JoelSherrill
Comment:

/* Test Theory */ Add a description of theory.. statement coverage versus assembly coverage.

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v8 v9  
    1111= Test Theory =
    1212
     13
     14The goal of the coverage analysis testing is to ensure that every line of generated assembly in a particular configuration is executed by the test suite.  This is beyond statement level coverage in that we have to verify both paths of a C line like the following is executed:
     15
     16{{{
     17x = (y) ? z : a;
     18}}}
     19
     20That is one statement but includes a branch.  That makes it one point to cover when viewed using statement coverage.  But it is two points to cover in our full coverage of generated assembly.
     21= Full Branch Coverage =
     22
     23
     24TBD
    1325= Reasons Code is Not Executed =
    1426
     
    2537
    2638 *  Critical sections which are synchronizing actions with ISRs.  Most of these are very hard to hit and may require very specific support from a simulator environment.  OAR has used tsim to exercise these paths but this is not reproducible in a BSP independent manner.  Worse, sometimes there is often no external way to know the case in question has been hit and no way to do it in a one shot test.  The spintrcriticalXX and psxintrcriticalXX tests attempt to reproduce these cases.
    27 = Full Branch Coverage =
    28 
    29 
    30 TBD
    3139= Test Procedure =
    3240