Once started, the
CCS4xConnector.js utility will try to connect to Debug Server, load the test binary, and execute it.
Before you run unit tests on an existing Code Composer project, you might need to perform some of the customizations described in Runtime Testing.
To run generated unit tests:
- Duplicate the "Builtin> Embedded Systems> Texas Instruments> Run TI CCS v4+ Tests" Test Configuration.
- Open the duplicated Test Configuration’s Execution> General tab.
- In the Execution details area, you can modify the following test execution flow properties:
- Target configuration file: This property points to the debugger configuration file that you want to use for your testing process. By default the "Active" (or, if that is not present, the "Default") target configuration file will be used. You can specify any path to a valid target configuration file. Note that your environment needs to be correctly configured for using this target (including GEL files initialization). C++test will only attempt to connect to the target as specified—without introducing any extra initialization.
- Executable exit point symbol: This property specifies the symbol that will be used for setting a breakpoint which will mark the end of test execution.
Debugging Test Cases
Use the standard means of executables debugging for TI Code Composer v4.
Before you run application monitoring on an existing Code Composer project, you might need to perform some of the customizations described in Runtime Testing.
To run application monitoring: