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.
Testing With the instrumented program, test execution by itself works as without instrumentation. The coverage data is written out during execution, for host applications typically directly to a data file ("MON.dat") .
Saving of Counters: When The coverage data is written out from main memory by default at the end of the program execution. There are several alternatives how to trigger this.
With Pragmas With #pragma CTC APPEND, the saving of coverage data is triggered.

With Pragmas

With #pragma CTC APPEND, the saving of coverage data is triggered.

This pragma can be put everywhere in the code where an executable statement can reside. It maps to a call to the run-time library of Testwell CTC++. Whenever it is executed, the execution counters that are collected at the time are saved to the data file. If the data file is saved many times during the program execution, it does not cause bias to the counters. In this arrangement, some source files need to be modified.