Project Test Parameters

This window lets you view and edit parameters that apply to the current project test. To open this window, click the Project button in the Project Testing UI tool bar.

Descriptions of Project Test Parameters tree branches are divided into three categories:

• Project Test Parameters - Static Analysis
• Project Test Parameters - Dynamic Analysis
• Project Test Parameters - Common Parameters, Search Parameters, Classes in Project

CLASSPATH Requirements

You must satisfy all of the following requirements in order to use the minimum Jtest functionality:

• The '.class' files for the classes you want to test must be available. A '.class' file is a compiled Java source. Without a '.class' file, Jtest will not be able to perform any tests.
• The '.class' files must be in a directory hierarchy that reflects the structure of the package, regardless of whether they are in jar files, zip files, or in the file system.
• The classes referenced by the tested '.class' files must be available to Jtest. This is done by adding their location to the CLASSPATH.
• If the '.class' files are in directories, '.zip' files, or '.jar' files, the '.class' files must be accessible by Jtest.

If during testing, Jtest finds ClassNotFoundExceptions or NoClassDefFoundErrors, or if it reports that it could not find the package on "imports", the CLASSPATH is not set properly. If this occurs, you need to set the system CLASSPATH variable to include every class referenced (recursively) by the tested class prior to testing. Check that the CLASSPATH includes the parent directory of the directory hierarchy. For example, if you are testing com.company.MyClass and Jtest reports that it could not find a package referenced by MyClass, it is probably because the 'com' directory is not on the CLASSPATH.

You can override the CLASSPATH environment variable in the Global Test Parameters, the Class Test Parameters, or the Project Test Parameters.