This section explains how to configure and run runtime testing. It covers:
C++test provides the following Test Configurations to run tests using TRACE32 tools:
Test Configurations can be customized using the following test execution flow properties:
Test executable exit point: The value of this property will be used to set a break point (Break.Set debugger command) that will mark the end of test execution. Typically, _exit symbol or similar should be used for this purpose.
Lauterbach TRACE32 test configurations automate:
Test executable uploading, execution and results collection is performed with help of a Lauterbach PRACTICE II script that is generated by C++test. The script is generated based on a template available in
You can customize this template as needed. To use a customized version of this script template:
Modify the Test Configuration’s test flow definition to use the customized version rather than the original script template. The script template path is specified in a flow step with id="db_scr_gen".
The "Embedded Systems/Lauterbach TRACE32/Run Tests using TRACE32 (FDX)"Test Configuration is provided to facilitate the unit testing process.
To run unit testing using TRACE32:
Use External Embedded debugging mode. For more details see:
To run application monitoring using TRACE32:
For general information on performing application monitoring and runtime error detection with C++test, see Runtime Error Detection.