Component Testing for Java Settings
Graphical User Interface
Diagram only when they change. This affects both trace size and UML Sequence
Diagram display size, but has no impact on execution time.
·
Check 'const' methods: Usually C++
const
methods are not checked for state
changes because they cannot modify a field of the
this
object. Instead,
const
methods are only evaluated once for invariants. In some cases, however, the
this
object may change even if the method is qualified with
const
(by assembler
code, or by calling another method that casts the
this
parameter to a non-const
type). There may also be pointer fields to objects which logically belong to the
object, but the C++ Test Script Compiler will not enforce that these pointed sub-
objects are not modified. Select this option only if your code contains such code
implementations.
·
Reentrant object support: Select this option if your application is multi-threaded
and objects are shared by several threads. This ensures atomicity for state
evaluation. This option has no effect if multi-thread support is not activated in
the Target Deployment Compilation Settings.
·
Enforce 'const' assertions: When this option is selected, the compiler requires
that invariant and state expressions are constant. Disable this option if you do
not use the
const
qualifier on methods that are actually constant.
To edit the Component Testing for C++ 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 C++.
4. Select
Files, General, Testing or Contract Check.
5.
When you have finished, click OK to validate the changes.
Component Testing for Java Settings
The Component Testing settings for Java are part of the Configuration Settings dialog
box, which allows you to configure settings for each node in your workspace.
The Component Testing for Java node settings lets you to customize the parameters
for the Component Testing for Java feature of Test RealTime.
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.
Mode Settings
This area contains parameters to be sent to the linker during the build of the current
node.
285
