The section includes:
In order to be able to automate runtime testing on the HEW IDE, a HEWTargetServer component must be registered into the HEW installation. To do this:
3. Browse to ${hew_install_dir}\\System\SEC\HewTargetServer\EcxHewTargetServer.hrf
then click Select.
If registration completes successfully, a HewTargetComponent should appear under "Extension Components"
4. Click OK.
For additional details, see the HEWTargetServer User's Manual that is provided by Renesas.
The configurations for testing on the simulator use the HEW simulation capabilities to run the prepared test executable. Testing results are sent using the HEW Simulated I/O feature.
The following steps are required to configure the HEW IDE:
The C++test instrumentation should be disabled for low level C code files (typically, dbsct.c, lowsrc.c, resetprg.c and sbrk.c) to ensure that the test executable has a proper execution flow. To disable instrumentation for such files, clear the Parasoft> C++test> Execution settings> Instrument selected source files(s) field in the mentioned files’ properties.
The Test Configurations provided to execute runtime tests for HEW projects (“Builtin> Embedded Systems> Renesas HEW”) may require environment-specific customization. The typical customizations are done with the help of test flow definition properties that are listed for each Test Configuration (in the Execution> General tab, "Execution details" section).
The table below describes the test flow properties for the Renesas HEW dedicated built-in Test Configurations:
Name | Default Value | Description |
---|---|---|
Workspace file to load | ${hew:workspace_file} | Automatically expanded to the location of the HEW workspace file. If it is not automatically detected by C++test, you need to specify it manually. |
Debug session | ${hew:current_session} | Automatically expanded to the last used session in the HEW IDE. Can be specified manually. |
Simulated I/O address | ${hew:simulated_io_address} | Simulated I/O address, as configured in the HEW IDE debug session. Automatically expanded to the proper value from debug session. If it is not automatically detected by C++test, you need to specify it manually. |
The following test configuration is provided to facilitate the unit testing process:
To run unit testing on the simulator:
C++test does not support direct Test Cases debugging for this environment.
Use standard means of executables debugging.
The following test configuration is provided to facilitate the application monitoring process:
To run application monitoring on the simulator: