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.
Integrating with Build SystemsOn the lowest level, ctc is always responsible for instrumentation of single source files. For the large variety of build systems, Testwell CTC++ provides several methods of integration without the need to interfere directly with the compiler call.
Switching between buildsWhen switching from a normal build to an instrumented build or from an instrumented build back to an uninstrumented build, depending on the build setup, a full rebuild can be necessary.

Switching between builds

When switching from a normal build to an instrumented build or from an instrumented build back to an uninstrumented build, depending on the build setup, a full rebuild can be necessary.

If you share build directories for instrumented and normal builds, this switching together with an incremental rebuild can lead to

source files that are not instrumented,
source files that are still instrumented in the object files, causing linker errors as the Testwell CTC++ runtime is missing.