fpc/tests
2003-09-14 12:56:28 +00:00
..
bench * old logs removed and tabs fixed 2002-09-07 15:40:30 +00:00
sparc + adding assmbling of prt0.as to the script 2003-06-02 22:05:56 +00:00
tbf * test is now passed successfully to be delphi compatible 2003-09-14 12:56:28 +00:00
tbs * Bugfix of procedrual variables of methods (Bug report 2588) 2003-08-09 11:38:52 +00:00
test * fix for m68k, extended are 12 bytes 2003-06-19 10:04:00 +00:00
units * create tmp installdir to install exe files 2003-05-09 16:31:05 +00:00
utils * fix a problem with KNOWNCOMPILE10ERROR 2003-06-13 08:16:34 +00:00
webtbf no message 2003-09-07 14:12:43 +00:00
webtbs + Added on florians request 2003-09-07 14:12:13 +00:00
.cvsignore digest generated files added 2002-12-05 16:05:16 +00:00
Makefile * compile win32err unit for win32 target 2003-04-30 21:21:05 +00:00
Makefile.fpc * compile win32err unit for win32 target 2003-04-30 21:21:05 +00:00
readme.txt + added more explanations 2002-11-09 22:02:36 +00:00

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.