diff options
| author | David Bremner <david@tethera.net> | 2015-09-24 08:13:30 -0300 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2015-09-25 09:18:22 -0300 |
| commit | 3cf7ed26c06fb3fa7145948fd9a9f2973037a5fd (patch) | |
| tree | 554b2f1ace385b52aa45a4c29a2ca76f2294a77c /test/README | |
| parent | 3c46a9e6df9ac736bf9462d3b16494069509e0e7 (diff) | |
test suite: don't consider skipped individual tests as failing
It isn't completely clear what we want to do here, but
1) We currently don't fail if we skip a whole test file (mainly because
we neglect to count those skipped tests properly). This change at least
makes the two kinds of skipping consistent.
2) Automated build environments may have good reasons for building with
a minimal set of prereqs, and we don't want to discourage running our
test suite by breaking builds.
Diffstat (limited to 'test/README')
| -rw-r--r-- | test/README | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/test/README b/test/README index ce403cef..e54e36b7 100644 --- a/test/README +++ b/test/README @@ -117,6 +117,13 @@ Note that some tests in the existing test suite rely on previous test items, so you cannot arbitrarily skip any test and expect the remaining tests to be unaffected. +Currently we do not consider skipped tests as build failures. For +maximum robustness, when setting up automated build processes, you +should explicitely skip tests, rather than relying on notmuch's +detection of missing prerequisites. In the future we may treat tests +unable to run because of missing prerequisites, but not explicitely +skipped by the user, as failures. + Writing Tests ------------- The test script is written as a shell script. It should start with |