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.
Incremental BuildsTestwell CTC++ handles incremental builds performed by the build system. The symbol file(s) must be kept from the consecutive builds.

Incremental Builds

Testwell CTC++ handles incremental builds performed by the build system. The symbol file(s) must be kept from the consecutive builds.

When the build system compiles only those source files changed since last build, Testwell CTC++ still needs the descriptions for the other source files in a symbol file for reporting. The symbol files from former builds can be kept separately or they can be reused during an incremental build. In the latter case, the descriptions of the changed source files are updated by ctc and the other descriptions stay as they are.