Generated Test Script
Test RealTime - User Guide
2.
In the file selector, select Trace Files (*.tsf, *.tdf) and select the .tsf and .tdf files
produced after the execution of the application under test.
3. Click
OK.
Generated Test Script
When a probed application is executed,
System Testing for C
produces a .pts test
script based on probe activity.
You can edit and reuse this script in further tests to replay the exact same data
exchanges in a System Testing for C test node.
Probe Output Modes
By default, the message traces are written to the .rio System Testing for C output file.
However, the Probe capability can send traces to a temporary buffer. To change the
way traces are stored, change the trace mode as specified in the Probe Control
Settings:
·
DEFAULT: In this mode, the message traces are written directly to the .rio
System Testing output file for C
·
FIFO: Select this to direct traces to a temporary
first-in firs out
memory buffer
before writing to the .rio file
t-
·
FILE: Select this to direct traces to a temporary file before writing to the .rio file
·
USER: Uses a method, described in a user-defined probecst.c file that must be
added to the application node
·
IGNORE: Use this setting to ignore trace macros.
When FIFO, FILE or USER are selected, the traces must be flushed to the .rio file with
a specific atl_dump_trace macro placed in the source code.
Customizing the Output Mode
The I/O functions for probe trace output to the temporary location are defined in the
probecst.c source file delivered with the product.
The implementation delivered with the product is based on a circular buffer. The
instrumented application sends traces to the circular buffer, by using the
atl_write_probe function. The traces can then be read by the atl_read_probe function.
You can modify this file to adapt the probe mechanism to your application and
platform.
234
