peter ec93a88048 * cthreads is unix only 21 år sedan
..
bench 7fe57a2396 * fixed time calculation 22 år sedan
tbf 8fb9867f9c + Added tb0160 21 år sedan
tbs 46472dc0da * new macro expansion problem 21 år sedan
test ff064bf580 * pakcrecords test 21 år sedan
units 55850b063a * regenerating the makefiles with some netbsd fixes + version upgrades 21 år sedan
utils 853c78c4b6 * fixed compile 22 år sedan
webtbf 53818575d3 * new bugs 21 år sedan
webtbs ec93a88048 * cthreads is unix only 21 år sedan
.cvsignore 361a2f9396 digest generated files added 23 år sedan
Makefile c47ea819b2 + dir units\math to tests added 21 år sedan
Makefile.fpc c47ea819b2 + dir units\math to tests added 21 år sedan
readme.txt dc9c9e21f4 * readme extended 22 år sedan

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