From 65a7563edbbab8f93fe901f932065687508788de Mon Sep 17 00:00:00 2001 From: Justus Winter Date: Mon, 5 Sep 2016 13:59:29 +0200 Subject: tests: Update README. * tests/openpgp/README: Update. Signed-off-by: Justus Winter --- tests/openpgp/README | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-) diff --git a/tests/openpgp/README b/tests/openpgp/README index 9b384beb1..84faf1cdd 100644 --- a/tests/openpgp/README +++ b/tests/openpgp/README @@ -1,22 +1,36 @@ # Emacs, this is an -*- org -*- file. * How to run the test suite -** using the legacy driver -On POSIX you can just use +From your build directory, run - $ make -C tests/openpgp check + obj $ make -C tests/openpgp check -or +to run all tests or - $ make -C tests/openpgp check XTESTS="setup.scm your-test.scm finish.scm" + obj $ make -C tests/openpgp check XTESTS=your-test.scm -as before. -** using the Scheme driver +to run a specific test (or any number of tests separated by spaces). + +If you want to debug a test, add verbose=1 to see messages printed by +spawned programs to their standard error stream, verbose=2 to see what +programs are executed, or verbose=3 to see even more program output +and exit codes. + +** Passing options to the test driver + +You can set TESTFLAGS to pass flags to 'run-tests.scm'. For example, +to speed up the test suite when bisecting, do + + obj $ make -C tests/openpgp check TESTFLAGS=--parallel + +See below for the arguments supported by the driver. + +** Calling the test driver directly This is a bit tricky because one needs to manually set some environment variables. We should make that easier. See discussion below. From your build directory, do: - obj $ srcdir=/tests/openpgp \ + obj $ TMP=/tmp srcdir=/tests/openpgp \ GPGSCM_PATH=/tests/gpgscm:/tests/openpgp \ $(pwd)/tests/gpgscm/gpgscm [gpgscm args] \ run-tests.scm [test suite runner args] -- cgit v1.2.3