diff options
Diffstat (limited to 'doc/testrunner.md')
| -rw-r--r-- | doc/testrunner.md | 31 |
1 files changed, 22 insertions, 9 deletions
diff --git a/doc/testrunner.md b/doc/testrunner.md index c2808a1e4..d1696e9d1 100644 --- a/doc/testrunner.md +++ b/doc/testrunner.md @@ -53,6 +53,14 @@ A useful query might be: SELECT * FROM script WHERE state='failed' ``` +You can get a summary of errors in a prior run by invoking commands like +these: + +``` + tclsh $(TESTDIR)/testrunner.tcl errors + tclsh $(TESTDIR)/testrunner.tcl errors -v +``` + Running the command: ``` @@ -61,13 +69,17 @@ Running the command: in the directory containing the testrunner.db database runs various queries to produce a succinct report on the state of a running testrunner.tcl script. -Running: +A good way to keep and eye on test progress is to run either of the two +following commands: ``` watch tclsh $(TESTDIR)/testrunner.tcl status + tclsh $(TESTDIR)/testrunner.tcl status -d 2 ``` -in another terminal is a good way to keep an eye on a long running test. +Both of the commands above accomplish about the same thing, but the second +one has the advantage of not requiring "watch" to be installed on your +system. Sometimes testrunner.tcl uses the `testfixture` binary that it is run with to run tests (see "Binary Tests" below). Sometimes it builds testfixture and @@ -297,18 +309,19 @@ run a Tcl test script, as <a href=#binary_test_failures>described above</a>. <a name=fuzzdb></a> ## 3.4 External Fuzzcheck Databases -Testrunner.tcl will also run fuzzcheck against external (out of tree) -databases, for example fuzzcheck databases generated by dbsqlfuzz. To do -this, simply set the FUZZDB environment variable to the name of the external +Testrunner.tcl will also run fuzzcheck against an external (out of tree) +database, for example fuzzcheck databases generated by dbsqlfuzz. To do +this, simply add the "`--fuzzdb` *FILENAME*" command-line option or set +the FUZZDB environment variable to the name of the external database. For large external databases, testrunner.tcl will automatically use -the "`--slice`" command-line option of fuzzcheck to divide the work up between -multiple jobs, thus increasing parallelism. +the "`--slice`" command-line option of fuzzcheck to divide the work up into +multiple jobs, to increase parallelism. Thus, for example, to run a full releasetest including an external dbsqlfuzz database, run a command like one of these: ``` - FUZZDB=../fuzz/20250415.db test/testrunner.tcl releasetest + tclsh test/testrunner.tcl releasetest --fuzzdb ../fuzz/20250415.db FUZZDB=../fuzz/20250415.db make releasetest nmake /f Makefile.msc FUZZDB=../fuzz/20250415.db releasetest ``` @@ -318,7 +331,7 @@ databases. So if you want to run *only* tests involving the external database, you can use a command something like this: ``` - FUZZDB=../fuzz/20250415.db test/testrunner.tcl releasetest 20250415 + tclsh test/testrunner.tcl releasetest 20250415 --fuzzdb ../fuzz/20250415.db ``` <a name=testrunner_options></a> |