Techniques for systematic software testing, the first published example of Code Coverage was by Miller and Maloney in 1963.

Measuring code coverage can be done in a number of ways, the main ones being:

• Statement Coverage - Checks if each source code line been run and tested
  
• Condition Coverage - Checks if evaluation points been run and tested
  
• Path Coverage - Checks if each route possible through a specific element of the code been run and tested
  
• Entry/Exit Coverage - Checks if every call and return possible has been executed and tested
  
• Naturally there are a number of interconnections between the different types of code coverage

Source code is run through a series of tests and the results from that testing are then analysed to identify sections of the code that have not been run. The process is iterative and the results of each set of tests are included in subsequent tests as required. The overall aim of Code Coverage is to create a rigorous set of software tests and analysis that check the software is performing as expected and through re-testing to eliminate disfunctionality

Code coverage normally is shown as a percentage of the total code, whilst comparison within the same type is possible, it is not possible to compare between different types due to differences in comprehensiveness.

Please read the full articles on Code Coverage and Unit Testing

This website is a hub to enable users to identify tools for Code Coverage for C and for Java. If you use these tools please link to the site and check back for updates