Command Line Interface

HCL OneTest EmbeddedOneTest Embedded 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 OneTest Embedded 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 OneTest Embedded test scripts into source files supported by your native compiler and linker:

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:

However, if the user would like compilation and linkage to immediately follow source code insertion, use the binaries:

The following sections provide details about the most common use cases.

 

To learn about

See

Launching the GUI with the studio command and running a node from the command line

Running a Node from the Command Line

Preparing your environment for command line usage

Setting Environment Variables

Code coverage, runtime tracing, memory and performance profiling from the command line

Command Line Runtime Analysis for C and C++

Command Line Runtime Analysis for Java

Testing C, C++ and Ada source code components from the command line

Command Line Component Testing for C, Ada and C++

Testing Java source code components from the command line

Command Line Component Testing for Java

Testing message-based systems from the command line

Command Line System Testing for C

Using the Command Line Interface through a set of examples

Command Line Examples

 

Related Topics

Using the Graphical User Interface | Automated Testing | Runtime Analysis