Compiling the Test Harness
Command Line Interface
A wide variety of compilation flags can be used by the command line tools, allowing
you to select sub-components of the application under test. These flags are equivalent
to the Test Configuration Settings dialog box of the graphical user interface and are
covered in the Reference Manual.
Default settings are contained in the following Perl script. You can use this file to
define your own customized configuration settings.
<InstallDir>/lib/scripts/BatchCCDefaults.pl
To run this script, type the following command:
$TESTRTDIR/bin/<cpu>/<os>/perl -I$TESTRTDIR/lib/perl
$TESTRTDIR/lib/scripts/TDPBatchCC.pl <my_env.pl>
where
<cpu>
is the architecture platform of the machine,
<os>
is the operating
system, and
<my_env.p >
is your customized copy of the BatchCCDefaults.pl file
l
The TESTRTDIR and ATLTGT environment variables must have been previously set.
Compiling the Test Harness
Each of the test compilers converts a test script into test harness source code. This
section explains how to compile the test harness source file.
Requirements
In order to compile a generated source file, you must check that:
·
A working C, C++ or Ada compiler is installed on your system
·
If you are using System Testing, you have prepared a valid options.h file
·
If you are compiling on a target different from the host where the file was
generated, the generated file must have been produced using the -NOPATH
option (available with every test compiler), and the /lib sub-directory of the
Target Deployment Port directory must be copied onto the target.
Compilation
If you are using Component Testing, System Testing or Component Testing for C++
alone without any of the runtime analysis features, then simply compile the
generated test harness source file with your C or C++ compiler.
If you are compiling on a remote target, do not forget to add to the
include
search
path the /lib sub-directory that you have copied onto the target.
If you are using SCI instrumentation features (Memory Profiling, Performance
Profiling, Code Coverage, Runtime Tracing and C++ .otc contract check), use the
specific command line options for the Instrumentor in the Reference Manual.
329
