Changes between Version 5 and Version 6 of Developer/Coverage/Theory

Timestamp:

09/10/09 01:15:28 (15 years ago)

Author:

GlennHumphrey

Comment:

Beginning to show example

Developer/Coverage/Theory

@@ -8 +8 @@
 The subject of Code Coverage Analysis is broad and has been written about many times over.  This background material is not intented to summerize or rehash what can be read elsewhere.  Instead, the focus here will be on the aspects of Code Coverage Analysis as they pertain to the [wiki:TBR/UserManual/RTEMS_Coverage_Analysis RTEMS Coverage Analysis] effort.
 
-The ultimate goal of Code Coverage Analysis is to ensure that every line of generated assembly in a particular configuration is executed by the test suite, that the tests exercise both taking and not taking every branch, and that every line of source code is actually tested.  In order to achieve this goal, several different coverage criteria may have to be examined.  Let's consider the following criteria:
+The ultimate goal of Code Coverage Analysis is to ensure that a test suite adequately tests a particular body of code.  In order to achieve this goal, several different coverage criteria may have to be examined.  Let's consider the following criteria:
 
  *  '''Object coverage''' - Has each line of generated assembly been executed?
@@ -16 +16 @@
  *  '''Modified Condition/Decision Coverage|Modified Condition/Decision Coverage (MC/DC)''' - Has every condition in a decision taken on all possible outcomes at least once? Has each condition been shown to affect that decision outcome independently?
 
+Each of these criteria can be used independently to analyze the code in question.  But there are clear relationships between the different criteria as shown in the picture.  It is important
+
 [[Image(CoverageCategories.png)]]]]
 
-This is beyond statement level coverage in that we have to verify both paths of a C line like the following is executed:
+If we consider the following example
 
 {{{
-x = (y) ? z : a;
+if (x || y)
+  do something
 }}}
 
-That 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 object level coverage of generated assembly.
+and its psuedo object code
+
+{{{
+cmp x, 0
+branch if FALSE to do something
+}}}
 = Object Coverage =