Compile the programs jtarccat, jtarcget and jtarcput. We suggest adding jikestst/bin to your PATH; otherwise, you will need to put copies of the scripts and executables to a directory on your PATH.

    cd jikestst/bin
    make

Tests are run using the jt script which takes as input test description files with type .d.

The jt script uses Jikes; js is similar, but uses another compiler, usually Sun's javac, for comparison purposes.

The script jtgen is like jt; however, while jt executes commands, jtgen just writes out commands to be executed later. This is useful in debugging multi-file tests.

Suitable changes are probably needed for the definition of COMP in the files js, jt, jsm and jtm (unless your username happens to be shields!).

The test scripts take as input a descriptor file for a set of tests. Each line in the descriptor file has the form:

    command arguments

#

comment

c file class

copy source file file.java to file local class.java and compile it, saving compiler output in file.c

e file class

copy source file file.java to local file class.java compile it, and then execute class, saving output in file.e

g file package class

copy source file file.java to package/class.java

f package class

compile package/class.java, appending compiler output to package.c

m name directory_list

start multi-file test with name name, directory_list is a list of directories that should be created in an empty state.

Q

quit

r directory-list

erase each directory in the directory list

s directory

set the directory to be searched for source files (default ../src)

x name args

execute name.class with arguments args. The default for name is Test.

The c and e commands are used for single file tests. The arguments are the file name and an optional class name. If the class name is not given, Test is assumed. A c (or comp) test just compiles the file, an e (or exec) test compiles a file and executes the resulting class file.

Tests requiring more than one file take the form

    m name directories
    g ...
    f ...   
    x ...

where the intial m command names the tests and gives a list of directories needed if packages are involed. The g command is used to copy the source files, and the f command is used to compile them. The x command is used to execute the program.

Run the tests as follows (be sure that the definition of COMP in jt points to the executable that you are testing):

    cd jikestst/derek/w
    make exec
    make chk
    cat exec.dif   // examine the output
    cd jikestst/hpj/w
    make exec
    make chk
    cat exec.dif   // examine the output

These tests are intended mainly for regression testing and are by no means meant to be interpreted as a comprehensive test of compliance or conformance.