Code coverage

Target Computer Coverage of Design Coverage of Code Coverage of Control and Data Coupling Lifecycle environment control is established Processes comply with plans and standards Process transition criteria satisfied Conformity review conducted... 

Coverage of Code Results of structural coverage analysis, and reviews/ inspections of code coverage analysis. 

To estimate the probability of failure per demand, we first require an estimate for the number of residual faults (N). A theory was developed in [Bishop 2002b] that relates the code coverage achieved with the number of residual faults. This is based on the concept of executing a boverage element which is some part of the code structure, e.g. a program statement, a program block between decision points, a program branch, etc. The theory assumed that ... 

Bishop 2002b] P.G. Bishop, Estimating Residual Faults from Code Coverage , Safecomp 2002, pp. 163-174,Catania, Italy, 10-13 Sep. 2002. 

Our quality assurance effort on H-VAD software consists of two parts code coverage measurement in in-vitro environment using blood-like liquid and live animal testing conducted in close consultation with KAOC staff and in compliance to the relevant guideline. 

In-Vitro environment testing and code coverage measurement... 

In the animal experiment, we observed that 166 out of 211probing statements (78.7%) were covered. This small difference in coverage was caused by onr inability to repeat certain test cases so as not to endanger the animars life. We therefore concluded that there was virtually no difference in code coverage between the... 

This approach can be used as a tool to define differentiated test approaches for the components in each quadrant. Formal test techniques and extended reviews can be applied to components in quadrant I, while components in quadrant IV are tested only informally or maybe not at all (no risk - no test). It is also possible to differentiate the test approach with different code coverage criteria for the different quadrants. 

A condition is a Boolean expression (e.g., IF). A decision is a Boolean expression composed of conditions and Boolean operators (e.g., AND, OR). A decision without a Boolean operator is a condition. Typical code coverage criteria include the following ... 

The amount of code coverage testing that should be performed depends on the safety certification level desired for the software. The most stringent coverage, MC/DC testing (or equivalent), is required by the Radio Technical Commission for Aeronautics (RTCA)/DO-178B for Level A software certification. 

Multi-core Testing and Code Coverage Ian Broster and David George, Rapita Systems, UK. 

Moreover, this optimization will inevitably reduce the overall level of safety that the system can aspire to (common mode hardware and code coverage) but maintains a generally satisfactory level. 

---