Optimizing Execution Traces

System Testing for C

Each Virtual Tester generates a trace file during its execution. This trace file is used to generate the System Testing Report.

You may want to adapt the volume of traces generated at execution time. For example, each Virtual Tester saves its execution traces in an internal buffer that you can configure.

To optimize execution trace output, use the Execution Traces area in the Test Script Compiler Settings dialog box.

By default, System Testing generates a normal trace file.
Select Time stamp only to generate traces for each scenario begin and end, all events, and for error cases. This option also generates traces for each WAITTIL and PRINT instruction. Use this option for load and performance testing, if you expect a large quantity of execution traces and you want to store all timing data.
Select Block start/end only to generate traces for each scenario beginning and end, all events, and for all error cases.
Select Error only to generate traces only if an error is detected during execution of the application. This report will be incomplete, but the report will show failed instructions as well as a number of instructions that preceded the error. This number depends on the virtual tester trace buffer size. Use this option for endurance testing, if you expect a large quantity execution traces.

In addition to the above, you can select the Circular trace option for strong real-time constraints when you need full control over the flush of traces to disk. If you want to still store a large amount of trace data, specify a large buffer.