florian e77d88c06e no message 22 ani în urmă
..
bench 952e80a72f * old logs removed and tabs fixed 23 ani în urmă
tbf d0b694e633 * 1.0.x test only 22 ani în urmă
tbs 9825fadb99 * fixed compilation of ppc system unit 22 ani în urmă
test 907d811e2e * removed wrong object size checks in static methods 22 ani în urmă
units 9fc4e555dd * regenerated 22 ani în urmă
utils 4610b0f576 * cosmetic fix in console output 22 ani în urmă
webtbf e77d88c06e no message 22 ani în urmă
webtbs 404d7fdc70 no message 22 ani în urmă
.cvsignore 361a2f9396 digest generated files added 23 ani în urmă
Makefile dcd54eeeed * -al isn't necessary anymore 22 ani în urmă
Makefile.fpc dcd54eeeed * -al isn't necessary anymore 22 ani în urmă
readme.txt dc9c9e21f4 * readme extended 22 ani în urmă

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