Running the Test Harness or Application
Test RealTime - User Guide
Linking the Application
Once you have compiled all your source files, you need to link them to build an
executable. This section describes linkage specifics when using a test or runtime
analysis feature.
Requirements
In order to compile an instrumented source file, you must check that:
·
A working C, C++ or Ada linker is installed on your system
·
You have compiled every source file, including any instrumented source files,
of your application under test
·
If using a Component Testing for C, Ada or C++, or System Testing, you have
compiled the test harness.
·
You have compiled the Target Deployment Port library.
Linking
If you are using only runtime analysis feature (Runtime Tracing, Code Coverage,
Memory Profiling, Performance Profiling, C++ Contract Check), you just have to add
the Target Deployment Port library object to the object files linked together. If you are
using a test feature, you also have to add the tester object to the linked files.
Running the Test Harness or Application
Once you have produced a binary tester or instrumented application, you want to
run it in order to obtain test or SCI analysis information.
By default, the generated SCI dump file is named atlout.spt.
To run the test application binary:
1.
Check that the current directory is correct, relatively to the previously specified
trace file, if the trace files was specified with a relative path.
2.
Run the binary. When the application terminates, the trace file should be
available.
Splitting the Trace Dump File
When you use several features together, the executable produces a multiplexed trace
file, containing several outputs targeting different features from Test RealTime . By
default, the trace file is named atlout.spt.
Requirements
330
