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

In 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.

Typical situations were a partial instrumentation is useful are:

Unit test code shall not be instrumented.
Code from standard headers shall be excluded.
The source has to be instrumented in portions for very small embedded targets.

Note: It is also possible to exclude source files later from reports with ctcreport or ctcpost. This is necessary, for example, when an included file shall be instrumented, but the including file shall not be reported.