Changes between Version 53 and Version 54 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 17, 2009, 10:00:13 PM (10 years ago)
Author:
GlennHumphrey
Comment:

/* Resolving Uncovered Code */ Added one more sentence

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v53 v54  
    8484 *  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.
    8585
    86 In general, it is interesting to note that the resolution of uncovered code does not simply translate into additions to the test suite.  Often the resolution points to improvements or changes to the analyzed code.  This can lead to more intelligent factoring of the code or a code re-design that produces a simpler solution.  There is also the notion that just because the analyzed code is "good" the way it is does not mean that it should be rewritten to improve its testability.
     86In general, it is interesting to note that the resolution of uncovered code does not simply translate into additions to the test suite.  Often the resolution points to improvements or changes to the analyzed code.  This can lead to more intelligent factoring of the code or a code re-design that produces a simpler solution.  There is also the notion that just because the analyzed code is "good" the way it is does not mean that it should not be rewritten to improve its testability.  Code that is completely tested is '''always''' better.
    8787= Measuring Progress =
    8888