Test Compiler Settings
Test RealTime - User Guide
·
Check stub: If selected, Component Testing for Java checks simulated classes.
Use No to save memory on the target platform.
·
Display stub note: If the Check stub setting is set to Yes, this setting specifies
whether to display simulated class information in the Component Testing
sequence diagram.
To edit the Component Testing for Java settings for a node:
1. In
the
Project Explorer, click the Settings
button.
2.
Select a node in the Project Explorer pane.
3.
In the Configuration Settings list, expand Component Testing for Java.
4. Select
Files, General, Testing or Contract Check.
5.
When you have finished, click OK to validate the changes.
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 Compiler Settings
·
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
ma n()
function. Necessary
memory is then allocated on the execution stack.
i
·
Heap - allocate memory through a Target Deployment Port dynamic allocation
function, which is configurable.
·
Enable Generate Virtual Testers as a Thread (instead of as a process): Use this
setting to on multi-thread platforms.
·
Entry function name: Specifies the name of a main entry function.
·
Do not share user-defined Virtual Tester global variables: When using multiple
Virtual Tester threads, this setting allows you to specify global variables in the
test script that should remain unshared by separate Virtual Tester threads.
286
