Before you start the harness on a test system, you must
have a valid test suite and Java Development Kit 6.0 or higher installed on
your test system. See your test suite documentation for information about installing
the test suite on your test system. Refer to
http://www.oracle.com/products
for information about installing the
current Java Development Kit on your test system.
You must also understand how your test group uses or intends to use the harness in its test system. For example, consider the following questions:
Does your test group use the harness and one or more agents to run distributed tests?
If you use an agent to run tests, you must also install the agent on the platform being tested. If you intend to use the JavaTest agent, see JavaTest Agent User's Guide for detailed information about installing the harness agent on a test platform. If you use a custom agent, refer to your test suite documentation for detailed information about installing the agent.
Does your test group use configuration files and templates from a central location, or does it use individual configuration files customized for each test run?
If your group intends to use configuration files and templates from a central location, the location must be configured for the harness to access the template files.
Does your test group run the harness from a central location or from local installations in the test system?
If your group uses a central location for the test system, you must be able to access the test system at that location.
It is extremely important to note that the JavaTest installation and runtime system is fundamentally a developer system that is not specifically designed to guard against any malicious attacks from outside intruders. If sample code or tests you author make a network call, you can expose the JavaTest operating environment during execution. For this reason, it is critically important to observe the precautions outlined in the following security guidelines when installing and running JavaTest.
The harness itself is self-contained in javatest.jar
. The only external dependency is jh.jar
, which should be placed either on the classpath or in the same directory as javatest.jar
. If desired, the following optional parts of the binary distribution can be deleted:
examples/
directory.doc/
directory.lib/jt-junit.jar
which is an optional binary component.To maintain optimum network security, JavaTest can be installed and run in a "closed" network operating environment, meaning JavaTest is not connected directly to the Internet, or to a company Intranet environment that could introduce unwanted exposure to malicious intrusion. This is the ideal secure operating environment when it is possible.
JavaTest does not require an "Intranet" connection that supports network connections to systems outside the JavaTest architecture to intra-company resources, but, for example, some Java ME applications in a test suite might use an HTTP connection. If JavaTest or applications launched from JavaTest are open to any network access you must observe the following precautions to protect valuable resources from malicious intrusion:
Install JavaTest behind a secure firewall that strictly limits unauthorized network access to the Java ME SDK file system and services. Limit access privileges to those that are required for JavaTest usage while allowing all the I-directional local network communications that are necessary for JavaTest functionality. The firewall configuration must support these requirements to run JavaTest while also addressing them from a security standpoint.
Follow the principle of "least privilege" by assigning the minimum set of system access permissions required for installation and execution of JavaTest.
Do not store any data sensitive information on the same file system that is hosting JavaTest.
To maintain the maximum level of security, make sure the operating system patches are up-to-date on the JavaTest host machine.