pierre 3897bcb765 * avoid failure on dummy test пре 23 година
..
bench 952e80a72f * old logs removed and tabs fixed пре 23 година
sparc 515af60a33 + more test to validate FPC/SPARC пре 23 година
tbf 40cedf1682 * 1.1 only, needed changes are to big for 1.0.x пре 23 година
tbs ff2d3b7d06 + also check shr 0 and shl 0 пре 23 година
test 3897bcb765 * avoid failure on dummy test пре 23 година
units 9addbba86a * regenerated пре 23 година
utils 27fbe5293a + newer functions made available under OS/2 пре 23 година
webtbf f1e708e298 * check that there is no internal error anymore пре 23 година
webtbs 4cd395a7c2 + new test пре 23 година
.cvsignore 361a2f9396 digest generated files added пре 23 година
Makefile 6e7c26a984 * regenerated after clean problem fix пре 23 година
Makefile.fpc 1b130d2aa8 * don't use INUNIX for clean rule пре 23 година
readme.txt b4f173c3c6 + added more explanations пре 23 година

readme.txt

The different directories are organized as follows:

webtbs...........Tests which should 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..............Manual database tests (success in compilation)
tbf..............Manual 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.