carl d67a1f12d9 + is operator testing 23 years ago
..
tbf 348ee97023 * new bug 23 years ago
tbs 2ba8f1d070 + added need compiler option 23 years ago
tesi 47758ec9fc + explicit .cvsignore files added 23 years ago
test d67a1f12d9 + is operator testing 23 years ago
units 927c693482 * fix source location in zips for packages and demos 23 years ago
utils 3b8a1581d8 + added support for OS/2 units (.ppo) 23 years ago
webtbf 3f639982d0 * moved to correct directory 23 years ago
webtbs cec813c1fa bug report test 23 years ago
.cvsignore 47758ec9fc + explicit .cvsignore files added 23 years ago
Makefile 927c693482 * fix source location in zips for packages and demos 23 years ago
Makefile.fpc a329d5e4f1 + add objects and cg directories to clean 23 years ago
readme.txt 1b364d873c + information on directory configuration and how to rerun the tests 23 years ago

readme.txt

The different directories are organized as follows:

webtbs...........Tests which succeed compilation
Digits in filename refer to bug database entry
webtbf...........Tests which should fail compilation
Digits in filename refer to bug database entry
test.............Some manual tests / testsuites
tbs..............Old database tests (success in compilation)
tbf..............Old database tests (fail compile)
units............Unit helper for doing the tests
utils............Utilities for processing tests


At the top of the test source code, some options
can be used to determine how the tests will be
processed (if processed automatically via make):

OPT...............Compiler option required to compile
CPU...............CPU Test target (i386,m68k,etc)
VERSION...........Compiler required to execute/compiler test
RESULT............Exit code of execution of test expected
GRAPH.............Requires graph unit
FAIL..............Compilation must fail
RECOMPILE.........????
NORUN.............Do not execute test, only compile it
KNOWN.............Known bug, will not be logged as bug
INTERACTIVE.......Do not execute test, as it requires user
intervention
NOTE..............Output note when compiling/executing test

To actually start the testsuite:
do a simple make full
This should create a log of all failed tests.