Running a Studio Node from the Command line interface

This feature applies to HCL OneTest™ Embedded Studio only.

Although the product contains a full series of command line tools, it is usually much easier to create and configure your runtime analysis specifications inside the graphical user interface (GUI). The CLI would then be used to simply launch the GUI with a project or project node as a parameter.

By doing this, you combine the ease and simplicity of the GUI with the ability to execute project nodes from a CLI.

Note: This functionality can be used to execute any node in a project, including group nodes, application nodes, test nodes or the entire project. You can also run your tests from the command line interface.

An HTML output option produces a set of HTML reports in a specified directory. The output is the same as exporting to HTML from the original reports. With this option, it is not necessary to open the GUI to view the reports.

To run a specific node from a command line:
1. Set up and configure your project in the GUI.
2. Save your project and close the GUI.
3. Type the following command:

studio -r <node>.{[.<node>]} <project_file> [-html <directory>]

where:

<node> is the node to be executed.

<project> is the .rtp project file.

<directory> is the output directory for the optional HTML output.

The <node> hierarchy must be specified from the highest node in the project (excluding the actual project node) to the target node to be executed, with periods ('.') separating each item:

<node>{[. <node>]}

Example: The following command opens the project.rtp project in the GUI, and runs the app2 application node, located in group1 of the sub-project subproject1:

studio -r subproject1.group1.app2 project.rtp -html project/output

To run an existing test in an headless mode, use the test launcher TestRT_test. Run the testrt_test -help command to have the list of options that you can use to execute your test. You get the following usage and list of options:

testrt_test <launcher options> <instrum options> --<settings> <testScriptFile> <source files> -I<include directory> -D<macro> [-- <cflags>] [-CPPFLAGS- <CPPFLAGS>] [-PPFLAGS- <PPFLAGS>] [-LDFLAGS- <ldflags>]