florian 5e504a4e98 no message 22 년 전
..
bench 952e80a72f * old logs removed and tabs fixed 23 년 전
tbf 79935db87c * test is now passed successfully to be delphi compatible 22 년 전
tbs 33266a3a5f * Removed windows dependency 22 년 전
test e7b757fb32 * mmx is 1.0.x only 22 년 전
units 9fc4e555dd * regenerated 22 년 전
utils 16c39734dd * go32v2 fixed 22 년 전
webtbf aae403c0b4 * moved to webtbf 22 년 전
webtbs 5e504a4e98 no message 22 년 전
.cvsignore 361a2f9396 digest generated files added 23 년 전
Makefile 9fc4e555dd * regenerated 22 년 전
Makefile.fpc 46a9df017c * only add dbdigest when USESQL=YES 22 년 전
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.