                              TARGETD64
AN UNIVERSAL C64 ARCHIVE RELATED CONVERTER TOOL AND EMULATOR FRONTEND

TargetD64 homepage:
http://skyscraper.fortunecity.com/quadra/251/targetd64.html
Author: Karlheinz Langguth mailto:klangguth@netscape.net

~/testsuite/README: TargetD64 testsuite
---------------------------------------

The testsuite contains a lot of archived files that are processed by
TargetD64. A test case is named XXX_N (e.g. LHA_1) with XXX is the name
of the test series and N an ongoing number. The produced files are put into
a directory named after the test case XXX_N. The expected result files are
found in XXX_N.OK (e.g. LHA_1.OK).

Attention:
The tar archive which carries this testsuite includes symbolic links. This is
used to link equal result files to a prototype thus saving diskspace. So if your
OS does not support symbolic links the expected result directories will not be
extracted correctly. The automatic result verification only works for Linux so
it will be no big deal anyway.

Linux:

The results are compared automatically. The outputs to stderr and stdout
are compared as well. The files from XXX_N (produced results) are compared
to the files of XXX_N.OK (expected results). All errors are printed out on
the console.

The bash shellscript test.sh does the above described processing. To execute it
try: cd ~/testsuite; test.sh. 

The execution of the testsuite test.sh will also create the Win32 version
test.bat.

To successfully execute all test cases you will need to have a few tools
installed like cbmconvert, zip2disk, lha for UNIX, unzip, gunzip, tar.

These test cases are there to test the incorporation of external helper
applications. This is the former way of TargetD64 to extract archives. Now all
the major archives are intrinsic. So if some test cases fail take a look into
test.sh and see if there are external helper applications involved which are
not installed on your system.

With option "-c dir" it is possible to execute just a result verify. This is
ideal for checking results produced by Win32 if the Win32 filesystem is mounted.
The result directories in "dir" are scanned and compared to the expected result
directories in the current directory. Use: cd ~/testsuite; test.sh -c dir.

Win32:

In contrast to the Linux version there is no automatic result verification.
Blame this on the shell command syntax. Instead the test cases are only executed
and the result files are put into XXX_N (look above).

Some test cases are disabled for Win32 as well. Mostly those which incorporate
external helper applications as they are not the same for Win32 (DOS).

What I do is execute the testsuite for Win32 and do the comparison with Linux as
I have the Win32 filesystem mounted (using option -c on linux).

To execute the testsuite try:

cd ~\testsuite
test.bat
