Rhapsody Test Conductor

You can use Rhapsody TestConductor in combination with your target. Before you can do this, please create the Animation libraries, the Framework libraries and get familiar with the Embedded UML Target Debugger example first.

The current version of the Embedded UML Target Debugger contains a basic support for execution of Rhapsody Test Conductor test cases and target with feedback of the assertions into Rhapsody. This works technically like this:

The monitor command WSTMonitor_sendRTCInfo() is used, which has it's prototype defined in WSTMonitor.h.
This function can be called in Rhapsody generated test cases through the Test Conductor ASSERT macros. It will pass three integers to the Embedded UML Target Debugger. The interface of c uses the address of an unsigned integer array.
To enable mapping from the ASSERT macros to WSTMonitor_sendRTCInfo(), you have to make changes in a Test Conductor source file: TestConductor_C.c. You find an adapted version of this file in <your product>\Samples\Model\RTCAnimation. You should merge the changes around the WSTMonitor_sendRTCInfo() call in your current file which can be found in the Test Conductor directory.
The animation program on the PC will receive the information send by WSTMonitor_sendRTCInfo() and do two things:

It shows in the console window a text like ASSERTION=x,y,z where x, y and z are the values of the unsigned integers passed.
It appends a line with the same text to the file rtcass.rst in the 'current working directory' of the animation program. This program is launced via the batchfile Tools\LiveAnimation\LiveAnimation.bat. The file rtcass.rst must be removed prior to launching the animation program or it will just grow by always appending new assertion results.

You can have a look at the RTCAnimation sample model which comes with the product.
Before results of the test execution are shown in Test Conductor, you first need to exit the Embedded UML Target Debugger and then your IDE which has been launched by the Test Conductor.