Plain Text Output

The HTTP server provides plain text output that can be used for automated monitoring of the JavaTest harness during test runs. The plain text output does not include HTTP headings or HTML formatting and is intended for use by automated testing frameworks, not for viewing in web browsers. Consequently, future releases of the JavaTest harness will attempt to maintain the content formatting and URLs of this output.

Two types of JavaTest information can be accessed by automated testing frameworks:

• Version Information
• Harness Information

Accessing Version Information

The HTTP Server Version page displays version information about the JavaTest harness. You can display the HTTP Server Version page by choosing its link on the index page or by including /version at the end of the URL in the browser URL field:

Example:
http://129.145.162.75:1903/version

A dump of the version information is provided.

Example:
JavaTest 3.0.3 Built on 06 Feb 2002

Accessing Harness Information

The following strings access specific information about the JavaTest harness:

• /harness/text/config

  Currently provides, in java.util.Properties format, the Test Suite name location and work directory of the current harness configuration values.

  Example:
  testsuite.path=/export/scratch/sampleJCK-compiler-13a testsuite.name=J2SE Sample Compiler 1.3a TCK (JCK) workdir=/export/scratch/wdsc13a

• /harness/text/tests

  Provides in java.util.Properties format the initial tests used for the current test run.

  Example:
  url0=api/java_lang url1=api/java_util

• /harness/text/stats

  Provides, in java.util.Properties format, the current count of test results in the each state (pass, fail, error, not run). Whitespace is not present in the output:

  Example:
  Passed.=0
Failed.=151
Error.=54
Not_run.=1
  

  For performance reasons, the Not_run number usually equals the concurrency setting in batch mode and matches the "not run" number shown in the GUI when in GUI mode (Current Configuration view filter).

• harness/text/results

  Provides alternating lines of test name, test status.

  Example:
  lang/FP/fpl005/fpl00506m1/fpl00506m1.html
Error. context undefined for hardware.xFP_ExponentRanges
lang/FP/fpl005/fpl00506m2/fpl00506m2.html
Error. context undefined for hardware.xFP_ExponentRanges
vm/classfmt/atr/atrnew003/atrnew00301m1/atrnew00301m1.html
Failed. unexpected exit code: exit code 1
vm/classfmt/atr/atrnew003/atrnew00302m1/atrnew00302m1.html
Failed. unexpected exit code: exit code 1
vm/classfmt/atr/atrnew003/atrnew00303m1/atrnew00303m1.html
Failed. unexpected exit code: exit code 1
  

• /harness/text/state

  Indicates whether JavaTest is currently running. It will return one of the following:

  running=true
running=false
  

• /harness/text/env

  Provides, in java.util.Properties format, the current environment settings for the test run.

  Example:
  command.testExecute=com.sun.jck.lib.ExecJCKTestOtherJVMCmd /work/jdk1.3.1/bin/java -classpath $testSuiteRootDir/classes -Djava.security.policy=$testSuiteRootDir/lib/jck.policy $testExecuteClass $testExecuteArgs context.nativeCodeSupported=true description=bar jniTestArgs=-loadLibraryAllowed nativeCodeSupported=true platform.expectOutOfMemory=true