peter a073d5f6b3 * new bug пре 22 година
..
bench 952e80a72f * old logs removed and tabs fixed пре 23 година
tbf 6939e0e4d4 * removed knowncompilererror10 пре 22 година
tbs f51646dfd5 * test exitcode 217 пре 22 година
test 0ab0eb77e3 * move extended size check to separate test пре 22 година
units ef20e6364a * 1.1 does not need fcl anymore пре 22 година
utils 853c78c4b6 * fixed compile пре 22 година
webtbf 5f71a74d25 * test must fail пре 22 година
webtbs a073d5f6b3 * new bug пре 22 година
.cvsignore 361a2f9396 digest generated files added пре 23 година
Makefile 05d37c8126 * $(OPT) added to dbdigest line пре 22 година
Makefile.fpc d72f8b3420 * added to dbdigest line пре 22 година
readme.txt dc9c9e21f4 * readme extended пре 22 година

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.

make rundigest scans the created log file and outputs some statistics
make rundigest USESQL=YES sends the results to an SQL database