Target Deployment Port options

Common Options

The following options pertain to the Component Testing for C++ feature.


Option	Description
ATO_CAST_PRINT_BUFFER_SIZE	This macro defines the size of the buffer devoted to the PRINT instruction. This buffer must be large enough to contain the output of a single PRINT instruction. If memory is an issue, you can set this value to 0. In that case, a single PRINT instruction will result in several notes in the graphical report, one per argument.

C++ Test Driver Script Options

The following options pertain only to C++ Test Driver Scripts.


Option	Description
ATO_USE_CAST	UsuallyATL_YES, this macro can be set toATL_NOif you are not using C++ Test Driver scripting. In this case, the Target Deployment Package object is smaller, and the compiler requires less memory to compile instrumented files.
ATO_CAST_STOP_ON_ERROR	When this macro is set toATL_YES, a function namedATL_Breakpointis called whenever an error occurs in the C++ Test Driver Script. In this case, you must provide this function, either by defining it incustom.hor by defining a macro naming your own breakpoint function incustom.h. You can thus set a breakpoint on this function and debug your test application when an unexpected result is encountered.
ATO_CAST_DUMP_SUCCESS	By default the value isATL_YES. This macro can be set toATL_NOif you do not want passed checks of your C++ Test Driver Script to be added to the trace file. This may be important if trace file size is an issue.
ATO_CAST_MAX_INSTANCES	This macro defines the maximum number of instances you expect to be used at the same time when running a C ++ Test Driver Script. An instance is pushed in a stack when aTEST CLASS,TEST SUITE, orTEST CASEis entered and when aPROCor aSTUBis called. Note that stubs can be recursive. The default value is 256. You can lower this value if memory is an issue and you know how many instances are used at the same time. You can increase it if your script is complex or if you use many stubs that call themselves or each other.

C++ Contract Check Script Options

The following options pertain only to the C++ Contract Check Scripts.


Option	Description
ATO_USE_AC	UsuallyATL_YES, this macro can be defined toATL_NOif you are not using C++ Contract Check scripting. In this case, the Target Deployment Package object is smaller, and the compiler requires less memory to compile instrumented files and generated files.
ATO_AC_STOP_ON_ERROR	When this macro is set toATL_YES, a function namedATL_Breakpointis called whenever an error occurs in the C++ Contract Check Script. In this case, you must provide this function, either by defining it incustom.h, or by defining a macro naming your own breakpoint function incustom.h. You can thus set a breakpoint on this function and debug your test application when an unexpected result is encountered.
ATO_AC_DUMP_SUCCESS	UsuallyATL_YES, this macro can be defined toATL_NOif you do not want passed checks of your C++ Contract Check Script to be added to the trace file. This may be important if the trace file size is an issue.
ATO_AC_FILE_NAME	This macro defines the default trace file name when executing the C++ Contract Check Script instrumented application. This name is used if you have not provided theGetEnvironmentmacro or$ATO_TRACESor$ATT_TRACES(%ATO_TRACES%or%ATT_TRACES%on Win32 platforms) environment variables, and if you are not using C++ Contract Check scripting.
ATO_AC_STRICT_CHECKING	When this macro is set toATL_YES, the invariants and states defined in C++ Contract Check Scripts are enforced to beconst. This implies that the compiler ensures that they do not modify any field of the object, and that they call onlyconstmethods. The default isATL_NObecause users often omit to specify theconstqualifier for methods that are actuallyconst. IfATL_NOis chosen, you must make sure that your invariants and state evaluations do not modify your objects.