fpc/tests
2002-07-28 09:45:24 +00:00
..
bench/shootout + Initial implementation 2002-06-05 20:30:50 +00:00
tbf * new bugs 2002-04-16 16:06:59 +00:00
tbs no message 2002-07-20 17:38:07 +00:00
tesi
test + case node testing 2002-07-28 09:45:24 +00:00
units * fix source location in zips for packages and demos 2002-03-19 19:36:55 +00:00
utils * fix compilation failure 2002-06-03 19:07:55 +00:00
webtbf + added 2002-06-12 18:01:06 +00:00
webtbs *** empty log message *** 2002-07-16 12:33:15 +00:00
.cvsignore
Makefile * fix source location in zips for packages and demos 2002-03-19 19:36:55 +00:00
Makefile.fpc
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.