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.

Integrating with Build Systems

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

ctclaunch and ctcwrap interact with build tools and build scripts directly, taking a call of the build system as command-line argument. There is no need to provide a dedicated build configuration for coverage measurement with these tools.
For Visual Studio and IAR Embedded Workbench, integrations are available for the IDEs and the underlying build system.
Build systems like make or IDEs like Eclipse can be configured to expand calls of the compiler to ctc calls.