<< Component Testing for C++ Settings | Component Testing for Java Settings >>

Contract Check Options

Test RealTime - User Guide

Call breakpoint function on CHECK failure: Select this option to call a
breakpoint function whenever a check failure occurs in an .otd Test Driver
script. To use this feature, you must set a breakpoint on the function
priv_check_failed (), located in the

<target_dep oyment_port>

/lib/priv.c, file.

You can use this option for debugging purposes.

Report only failed CHECKs: Select this option to hide passed tests in the UML
Sequence Diagram generated by Component Testing for C++. Only failed
checks are displayed. This option also reduces the size of the intermediate trace
file.

Instances stack size: This value defines the maximum level for C++ Test Driver
Script calls that you expect to reach when running an .otd Test Driver script.
The C++ Test Driver Script calling stack includes RUN, CALL and STUBs. The
default value is 256 and should be large enough for most cases. When using
recursive stubs, you may need to increase this value.

Display all PRINT arguments in a single note: Select this option to display only
one UML note for all arguments of a PRINT statement in the Component
Testing for C++ UML Sequence Diagram. This option requires use of a PRINT
buffer, which uses memory on the target machine. Disable this option if
memory on the target is an issue. In this case, Component Testing for C++
generates one UML note for each argument of each PRINT statement.

PRINT buffer size (bytes): With the previous option selected, this option defines
the size, in bytes, of the buffer devoted to the PRINT instructions during the
execution. This buffer should be large enough to handle the complete result of a
PRINT instruction. You may have to increase this value if your PRINT
statements contain many arguments, or if arguments are long strings.

Contract Check Options

These options are used by the C++ Contract-Check Script.

Call breakpoint function on assertion failure: Select this option to call a
breakpoint function whenever an assertion failure occurs in an .otc Contract
Check script. To use this feature, you must set a breakpoint on the function
priv_check_failure (), located in the

<target_dep oyment_port>

/lib/priv.c, file.

You can use this option, for example, to debug your application when an
assertion fails.

Report only failed assertions: Select this option to hide passed assertions in the
UML Sequence Diagram generated by Component Testing for C++. Only failed
assertions are displayed. This option also reduces the size of the intermediate
trace file.

Trace unchanged states: Select this option to report states in UML Sequence
Diagram generated by Component Testing for C++ each time states are
evaluated. If the option is disabled, states are reported in UML Sequence

284