background image
<< To activate System Testing dynamic tracking | Generated Test Script >>
<< To activate System Testing dynamic tracking | Generated Test Script >>

Using Probe Macros

Automated Testing
The use of C macros offers extreme flexibility. For example, when delivering the final
application, you can leave the macros in the final source and simply provide an
empty definition.
Using Probe Macros
Before adding probe macros to your source code, add the following #include
statement to each source file that is to contain a probe:
#include "atlprobe.h"
The atl_start_trace() and atl_end_trace() macros must be called when the application
under test starts and terminates.
Other macros must be placed in your source code in locations that are relevant for the
messages that you want to trace.
The following probe macros are available:
· atl_dump_trace()
· atl_end_trace()
· atl_recv_trace()
· atl_select_trace()
· atl_send_trace()
· atl_start_trace()
· atljpegtrace()
Please refer to the Probe Macros section in the Test RealTime Reference Manual for a
complete definition of each probe macro.
To activate the trace probe feature:
1.
In the Project Browser, select the application or test node on which you want to
use the feature.
2.
Click Settings and open the Probe Control Settings box.
3. Set
Probe Enable to Yes, select the correct output mode in Probe Settings and
click OK.
4.
Edit the source code under test to add the trace probe macros, including the
#include line.
5.
Set up your trace probes within your application source files.
To read the trace probe output:
1. From
the
File menu, select Open and File.
233