TCK Harness 

The code in this project comprises the DTFJ API TCK harness.  The testcases
reside in the org.apache.kato.tck.tests project

Objectives 

The objective of this harness is to provide a framework and excution system for 
producing dumps from a JVM and then running the TCK test suite against the dump
Since there are multiple forms of dump and multiple JVMs the harness has been designed
to be very configurable.


Setup

Once you have checked out the harness and testcases projects you will also need to check out
the projects that contain the required JVM implementation code. 

The harness project contains two example files.   These files show to configure the TCK for
your machine environment and for a specific test execution.

The example.local.properties file should be copied and renamed to tck.properties in your user directory.  
This is the same location as would be presented if you examined the java  user.home system property.
It is necessary to change the properties to reflect the locations of the files on you system.
The file contains properties that will be used by the harness to locate the required Java launchers etc.
More information about TCK properties is available in the properties.readme file.

The example.instance.properties file is an example of how to configure a specific execution run.
The file contains properties to set that indicate to the harness the JVM to use and what testcases
to execute.  These properties are also described in the properties.readme file.  To use this example file
create a copy (any name is acceptable) in a location of your choice.   The name and location of this file
will be used to launch the TCK harness


Executing the Test Suite

Executing the harness is a simple as running the  main method in the org.apache.kato.tck.harness.TCKLauncher class
The expected use is to pass in the instance properties file name and location as the first parameter. Note that 
by default the harness expects the classpath of the launcher to contain references to all required classes.  This 
includes JUnit 3.0.

At the start of execution the harness copies the instance property file into its working directory and renames it
to tck.properties. This is to allow easy debugging of failing testcases.


Executing a Single Testcase

In the event that the test suite has a failing testcase the test case can be launched directly as a standard
JUnit testcase.  The testcase will be self configuring and will look for the tck.properties file in the harness
working directory.  Note that any required environmental variables and jvm arguments are not set when running in
self hosting mode.