Home
General Working PrinciplesTestwell CTC++ measures Code Coverage for desktop / host applications and for embedded software. It works in three fundamental steps: instrumenting, testing and reporting.
Testing With the instrumented program, test execution by itself works as without instrumentation. The coverage data is written out during execution, for host applications typically directly to a data file ("MON.dat") .
Saving of Counters: When The coverage data is written out from main memory by default at the end of the program execution. There are several alternatives how to trigger this.
Using Selected Functions With the configuration parameter EMBED_FUNCTION_NAME, a list of functions can be defined to trigger the saving of coverage data.

Using Selected Functions

With the configuration parameter EMBED_FUNCTION_NAME, a list of functions can be defined to trigger the saving of coverage data.

This configuration parameter has to be used at instrumentation time. The parameter value is a list function names. Wildcards may be used.

You could use this arrangement for example as follows:

ctcwrap ... -C EMBED_FUNCTION_NAME=foo,Cls::bar make ...

When instrumenting the source files, if a stand-alone function foo() or a member function Cls::bar() is met, logically a

#pragma CTC
				APPEND

line is inserted just before each return, throw and function end (if control can flow to the end).

With this arrangement, no source files need to be modified.