Using CA Application Test › Using the Workstation and Console with CA Application Test › Building Test Cases › Properties › Common Properties and Environment Variables

Common Properties and Environment Variables

HOT_DEPLOY

Points to a project-specific hotDeploy directory.

LASTRESPONSE

The response to the last executed step.

LISA_HOME

Points to the install directory, and is automatically set. This value includes a final slash. To reference a directory such as "examples," specify:

{{LISA_HOME}}examples

No slash is needed before the directory name.

LISA_HOST

The name of the system on which the testing environment is running.

LISA_JAVA_HOME

The Java VM to use. Set this property only if you do not want to use the built-in VM. If Java is not installed, DevTest uses the bundled JRE it comes with. You also must rename the jre directory in the install directory to something like jre_notinuse.

LISA_POST_CLASSPATH

Used to add information after the DevTest classpath. DevTest does not use the OS environment CLASSPATH variable. To add your own JARs after the DevTest classpath, use LISA_POST_CLASSPATH.

LISA_PRE_CLASSPATH

Used to add information before the DevTest classpath. DevTest does not use the OS environment CLASSPATH variable. To add your own JARs before the DevTest classpath, use LISA_PRE_CLASSPATH.

LISA_PROJ_NAME

The name of the project to which the current document belongs. LISA_PROJ_NAME refers to the main calling test project.

LISA_RELATIVE_PROJ_NAME

The name of the project to which the current document belongs. LISA_RELATIVE_PROJ_NAME refers to the project for the currently executing test or subprocess. If the test does not call any subprocesses, LISA_PROJ_NAME and LISA_RELATIVE_PROJ_NAME are the same.

LISA_PROJ_PATH

The fully qualified path of the project directory. The value is operating system-dependent. A backslash (\) is used as the separator character on Windows. A forward slash (/) is used as the separator character on other operating systems. The following example is based on a Windows installation:

C:\Program Files\LISA\examples

The one limitation to using LISA_PROJ_PATH in a Custom Java step is that the syntax {{LISA_PROJ_PATH}} is not supported. The Custom Java step invokes a Java compiler to compile the script and Java treats backslashes as escape characters in strings. Therefore, this specific string raises a compiler error. The workaround is to use LISA_PROJ_PATH as a variable. For example:

File f = new File ( LISA_PROJ_PATH );

LISA_RELATIVE_PROJ_PATH

The fully qualified path of the project directory of the currently executing test or subprocess. LISA_PROJ_PATH refers to the main calling test. See LISA_PROJ_PATH for details. If the test does not call any subprocesses, LISA_PROJ_PATH and LISA_RELATIVE_PROJ_PATH are the same.

LISA_PROJ_ROOT

The fully qualified path of the project directory. The value is operating system-independent. A forward slash (/) is used as the separator character on all operating systems, including Windows. The following example is based on a Windows installation:

C:/Program Files/LISA/examples

LISA_RELATIVE_PROJ_ROOT

The fully qualified path of the project directory of the currently executing test or subprocess. LISA_PROJ_ROOT refers to the main calling test. See LISA_PROJ_ROOT for details. If the test does not call any subprocesses, LISA_PROJ_ROOT and LISA_RELATIVE_PROJ_ROOT are the same.

LISA_PROJ_URL

The URL of the project directory. For example:

file:/C:/Program%20Files/LISA/examples

LISA_RELATIVE_PROJ_URL

The URL of the project directory of the currently executing test or subprocess. LISA_PROJ_URL refers to the main calling test. See LISA_PROJ_URL for details. If the test does not call any subprocesses, LISA_PROJ_URL and LISA_RELATIVE_PROJ_URL are the same.

LISA_TC_PATH

The fully qualified path of the directory where the test case is located.

LISA_TC_URL

The URL of the directory where the test case is located.

LISA_USER

The user that loaded the test case.