System Testing for C Settings

The Test Script Compiler settings are part of the System Testing node of the Configuration Settings dialog box, which allows you to configure settings for each node.

By default, the settings of each node are inherited from those of the parent node. When you override the settings of a parent node, changes are propagated to all child nodes within the same Configuration. Overridden fields are displayed in bold.

Test Script Compiler

Message definition files: Use the Add and Remove buttons to create a list of message definition files. These are source files that define the structure declarations required by Virtual Testers.
Generate virtual testers as threads: By default, virtual testers are generated as processes. Use this setting with multi-threaded applications.
Multi-thread entry point: Specifies the name of a main function to act as an entry point in multi-threaded applications.
Virtual Tester Memory Allocation Method: Allows you to allocate memory to the Virtual Tester for internal data storage.
- Static - use global static variables for internal data storage. This allows the Virtual Tester to run on systems that do not support dynamic memory allocation or that have limited execution stacks.
- Stack - store internal data in a local variable of the main() function. Necessary memory is then allocated on the execution stack.
- Heap - allocate memory through a Target Deployment Port dynamic allocation function, which is configurable.
Duplicate user-defined static global variables: When using multiple Virtual Tester threads, this setting allows you to duplicate static global variables for each thread. This allows multiple instances of a virtual tester to all run in the same process with their own variables.
Use TDP thread launcher: Specify Yes if the current TDP supports launching virtual tester threads. If not, then you must write a specific program to perform this task, and set this option to No. See Launching virtual tester threads for more information.
Additional options: Use this setting to specify extra command line options. In most cases this should be empty.
Continue en WAITTIL error: Select Yes to force the scenario to resume after encountering an error in a WAITTIL statement. You can use this setting to debug virtual testers.
Trace Buffer Optimization: See Optimizing Execution Traces.
- Select Time stamp only to generate a normal trace file.
- Select Block start/end only to generate traces for each scenario beginning and end, all events, and for error cases.
- Select Errors only to generate traces only if an error is detected during execution of the application.
Circular buffer: Select this option to activate the Circular Trace Buffer.
Trace buffer size (Kbytes): This box specifies the size - in kilobytes - of the circular trace buffer. The default setting is 10Kb.

Report generator settings

Display initial and expected values: the way in which the values assigned to each variable are displayed in the report. See Initial and Expected Values.
Report generated form: This option specifies the form of the report generated.
- Full: provides a full report of all variables for each test.
- All failed test variables: All the variables that are in a failed test are displayed. If all tests are passed, then the report is empty.
- Only failed variables: Only failed variables are displayed. If all tests are passed, then the report is empty.
Sort by time stamp: By default, the report is sorted by test script structure blocks. Select this option to force the report to follow a fully chronological order.

Advanced for System Testing Settings

Kill VT when RENDEZVOUS fails: Enable this setting to force the supervisor to kill any remaining virtual testers each time a RENDEZVOUS fails. This prevents uncontrollable processes from running on the computer.
RENDEZVOUS timeout (seconds): This specifies the timeout associated to RENDEZVOUS statements.
INTERRECV timeout (seconds): This specifies the timeout associated to inter-tester communications.
Agent target directory: Specifies the directory where system testing agent is located.
Run without deployment: This allows you to launch the test execution without going through the deployment phase.
Compress trace data: This option performs internal compression of trace data. Select this for hard real-time constraints. If you select NO, no compression of trace data is performed.
Trace data buffer size (bytes): Specifies the size of the trace data buffer.
On-the-fly tracing: This option enables on-the-fly tracing at Target Deployment Port level.
On-the-fly tracing buffer size (bytes): This specifies the size of the trace buffer for on-the-fly tracing. By default the buffer size is 4096 bytes.