You can run component test launch configurations in a "headless"
workbench (with no user interface for the development environment) from a
command line interface.
Before running component tests in headless mode:
- Your workspace must contain a valid test suite with at least one test
case.
- The component under test must be compilable.
- Agent Controller must be running on your machine in order to retrieve
test results. The Agent Controller is a daemon process that enables client
applications to launch host processes and interact with agents that coexist
within host processes.
- You must have a workspace containing one or more launch configurations
for component tests.
The development environment does not need to be running.
Note: You cannot
run several headless workbenches on the same workspace at the same time, nor
can you use a headless workbench while an Eclipse graphical user interface
has locked the workspace.
To run component test in a headless workbench,
you launch the command line mode application using the command <eclipse_dir>/jre/bin/java <virtual
machine options> -cp <eclipse_dir>/startup.jar
org.eclipse.core.launcher.Main <command line mode options> <eclipse
options>, along with your product configuration.
You
might need to append additional parameters to the commands, depending on your
operating system configuration. The parameters for launching the workbench
in your environment are located in the system configuration details under
System
properties in , where:
- <virtual machine options> are located under the eclipse.vmargs property.
- The main Eclipse options are located under the eclipse.commands property,
to which you add the workspace path using the Eclipse token -data.
- <command line mode options> refers to command-line
mode options. See the reference section for more information.
The results of the test execution are generated in a
report directory
located in the workspace.
Note: In some environments the length of a command
line might be limited. If you encounter errors due to a truncated command
line, try replacing parts of the command with variables.