background image
<< Component Testing for Java | Running a Node from the Command Line >>
<< Component Testing for Java | Running a Node from the Command Line >>

Command Line Interface

Command Line Interface
Rational Test RealTime was designed ground-up to provide seamless integration
with your development process. To achieve this versatility, the entire set of features
are available as command line tools.
In most cases when a CLI is necessary, the easiest method is to develop, set up and
configure your project in the graphical user interface and to use the studio command
line to launch the GUI and run the corresponding project node.
When not using the GUI to execute a node, you must create source files that can
execute Test RealTime tests or acquire runtime analysis data without conflicting with
the your native compiler and linker. In both cases that is, regardless of whether you
are attempting to execute a Test or Application node the native compiler and linker
do the true work.
For Test nodes, the following commands convert Test RealTime test scripts into
source files supported by your native compiler and linker:
attolpreproC for the C language
atoprepro for the C++ language
attolpreproADA for the Ada language
Java does not require a special command because the test scripts are already .java
files.
For Runtime Analysis, the primary choice is whether or not you wish to perform
source code insertion (SCI) as an independent activity or as part of the compilation
and linkage process. Of course, if no runtime analysis is required, source code
insertion is unnecessary and should not be performed. To simply perform source
code insertion, use the binaries:
attolcc1 for the C language
attolccp for the C++ language
attolada for the Ada language
javi for the Java language
However, if the user would like compilation and linkage to immediately follow
source code insertion, use the binaries:
315