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.
InstrumentingTo measure code coverage, an instrumented build for the code under test is needed. Hence Testwell CTC++ has to interact with the existing build system. Often, not all parts of the code shall be instrumented, hence a partial instrumentation is used.
Partial InstrumentationIn several situations, parts of the source code shall not be instrumented for coverage measurement, but still be compiled as a part of the project. Testwell CTC++ offers three ways to do that: On source file level, on function level, or inside the code.
Partial Instrumentation on Function LevelWith the configuration parameter SKIP_FUNCTION_NAME, single functions can be excluded from instrumentation.

Partial Instrumentation on Function Level

With the configuration parameter SKIP_FUNCTION_NAME, single functions can be excluded from instrumentation.

Functions can be excluded from the instrumentation of their files. With the configuration parameter SKIP_FUNCTION_NAME, a list of function names can be defined. The function names are separated with comma, and the wildcard * can be used.

Example from command line:

ctc –C SKIP_FUNCTION_NAME=foo2,Aclass::memb,*::closeX …

The parameter can also be stored in the configuration file ctc.ini.