ccovinstrument 0.20

ccovinstrument package contains instruments C/C++ code for test coverage analysis. SYNOPSIS ccovinstrument code.c > covcode.c ccovinstrument code.c [-f] -o covcode.c [-e errs] -f instrument fatal code as well as normal code Scans C/C++ source (before cpp) and inserts trip-wires in each code path to record execution. A number of error prone coding styles are also detected. Many of these ideas came from study of the highly regarded perl5 source code (and from my own coding experience. This approach (or almost any approach) to coverage analysis is NOT fullproof! Just because you exercise every code path does NOT mean you have exercised all possibilities. For example, consider the following code: char fetch_char(int xx) { static char *string = "Dr. Zorph Trokien"; if (xx < 0) { return 0; } else { return string[xx]; } } Unfortunately, you still have to be somewhat intelligent about designing your test scripts. However, assuming youre clever, you can use this tool to know when to stop writing more tests. Thus, thereby achieving test coverage. CCov SOURCE DIRECTIVES /* CCov: off */ Turns off coverage instrumentation. You probably dont want to analyze debugging code. /* CCov: on */ Turns on coverage instrumentation. /* CCov: jump if for do while else return */ Adds to the list of identifiers that cause a change in execution flow. In addition to the usual keywords, macros used by the perl core and XSUBs are included by default. /* CCov: fatal myexit croak panic */ Adds to the list of identifiers that cause a fatal exception. Instrumentation of these blocks is turned off by default. (You usually want to make sure the code is suppose to work works before you make sure that the code that isnt support to work works.) HOW DOES IT WORK? The instrumenter processes source code before it is seen by cpp. This helps you isolate your testing. Usually, you want to do test analysis on each library/application individually. A global analysis would cause you to test new code and all the libraries you are using (for every single application!). The instrumentor does not really use a lexer (tokenizer). The techniques are probably more similar to image processing than parsing. As you might imagine, this doesnt work in the general case. CCov tries to be forgiving, but it simply doesnt understand obfuscated code. Rather than calling it a bug, I think its an significant feature. Simple code probably has fewer bugs than complex code. Not only is this tool aimed at test coverage analysis, it is also helps you improve your coding style. There are still some rough edges, but I am mostly satisfied with the degree of strictness..

Requirements:	No special requirements
Platforms:	Linux
Keyword:	Analysis,  C C++,  Ccov,  Ccovinstrument,  Code,  Code For,  Coverage,  Libraries,  Programming,  Test,  Test Coverage,  Work
Users rating:	0/10