diff options
author | Heiko Schlittermann (HS12-RIPE) <hs@schlittermann.de> | 2015-08-19 18:18:22 +0200 |
---|---|---|
committer | Heiko Schlittermann (HS12-RIPE) <hs@schlittermann.de> | 2015-08-19 18:18:22 +0200 |
commit | 1b1fefe35b9dd49148a1e6e122d280b8e81987d5 (patch) | |
tree | 394d18bce79608655d7891af684aea16e76df093 /test/README | |
parent | db333d1af8c0b3038689f764aad2510fddf8b613 (diff) |
Testsuite: Update README about flavours
Diffstat (limited to 'test/README')
-rw-r--r-- | test/README | 21 |
1 files changed, 17 insertions, 4 deletions
diff --git a/test/README b/test/README index 7bf4ceea5..cdc240df0 100644 --- a/test/README +++ b/test/README @@ -213,10 +213,12 @@ THE RUNTEST SCRIPT ------------------ If you do not supply any arguments to ./runtest, it searches for an Exim -source tree at the same level as the test suite directory. It then looks for an -Exim binary in a "build" directory of that source tree. If there are several -Exim source trees, it chooses the latest version of Exim. Consider the -following example: +source tree at the same level as the test suite directory. A source tree +is a source tree, if it contains a build-* directory. + +It then looks for an Exim binary in a "build" directory of that source +tree. If there are several Exim source trees, it chooses the latest +version of Exim. Consider the following example: $ ls -F /source/exim exim-4.60/ exim-4.62/ exim-testsuite-x.xx/ @@ -260,6 +262,17 @@ There are some options for the ./runtest script itself: (If it turns out that most people prefer to use diff, I'll change the default.) + -FLAVOR <flavor> + -FLAVOUR <flavour> + This allows "overrides" for the test results. It's intended + use is to deal with distro specific differences in the test + output. The default flavour is "foo". If during the test + run differences between the current and the expected output + are found and no flavour file exists already, you may update + the "common" expected output or you may create a flavour + file. If a flavour file already exists, any updates will go + into that flavour file! + -KEEP Normally, after a successful run, the test output files are deleted. This option prevents this. It is useful when running a single test, in order to look at the actual output before it is |