Workflow in the IDE
The IAR add-on of Testwell CTC++ offers a full integration with IAR Embedded Workbench, for all steps from building to report generation.
Configuration
to configure the coverage level, the usage ofBuild
Use MON.sym is created in the project directory.
to build instrumented binaries. They replace the uninstrumented version. The symbol fileNote: Using Debug as build configuration is the most
convenient way, especially when using Testwell CTC++ for
the first time.
Note: If a build is performed automatically when running the debugger, this can overwrite the instrumented program. You can deactivate this automation in the IAR Workbench options.
Tests
With the instrumented binaries, execute the tests as usual with IAR Embedded Workbench - on the real target, or in a simulation.
For many targets, the standard implementation of the HOTA runtime library works, especially when the debugger is used for communication. If an adaption is necessary, see Constructing the CTC Runtime for the Target for details.
Coverage Data and Reports
With the default setup for HOTA, only one step is necessary to build reports: Use
to choose the report and to generate it.If you are using BITCOV, the coverage data reside in an array in memory and have to
be dumped first to a file:
- Use the memory screen of the IAR debugger to locate
CTC_array
. - Save it to the project directory with file format "intel-extended" and filename memory.hex.
After that, you can continue with
as described for HOTA.