emacs: Add new option notmuch-search-hide-excluded

[notmuch] / test / README

diff --git a/test/README b/test/README
index 3f54af58876f324a851565a1e8b16633b61d5b08..a81808b164f0cec0ec6c0010cb023fe77d7e098c 100644 (file)
--- a/test/README
+++ b/test/README
@@ -25,6 +25,7 @@ that you know if you break anything.
   - gdb(1)
   - gpg(1)
   - python(1)
   - gdb(1)
   - gpg(1)
   - python(1)

+  - xapian-metadata(1)

 
 If your system lacks these tools or have older, non-upgradable versions
 of these, please (possibly compile and) install these to some other
 
 If your system lacks these tools or have older, non-upgradable versions
 of these, please (possibly compile and) install these to some other


@@ -79,14 +80,6 @@ The following command-line options are available when running tests:
        As the names depend on the tests' file names, it is safe to
        run the tests with this option in parallel.
 
        As the names depend on the tests' file names, it is safe to
        run the tests with this option in parallel.
 

-Certain tests require precomputed databases to complete. You can fetch these
-databases with
-
-       make download-test-databases
-
-If you do not download the test databases, the relevant tests will be
-skipped.
-

 When invoking the test suite via "make test" any of the above options
 can be specified as follows:
 
 When invoking the test suite via "make test" any of the above options
 can be specified as follows:
 


@@ -144,6 +137,23 @@ detection of missing prerequisites. In the future we may treat tests
 unable to run because of missing prerequisites, but not explicitly
 skipped by the user, as failures.
 
 unable to run because of missing prerequisites, but not explicitly
 skipped by the user, as failures.
 

+Testing installed notmuch
+-------------------------
+
+Systems integrators (e.g. Linux distros) may wish to test an installed
+version of notmuch.  This can be done be running
+
+     $ NOTMUCH_TEST_INSTALLED=1 ./test/notmuch-test
+
+In this scenario the test suite does not assume a built tree, and in
+particular cannot rely on the output of 'configure'. You may want to
+set certain feature environment variables ('NOTMUCH_HAVE_*') directly
+if you know those apply to your installed notmuch). Consider also
+setting TERM=dumb if the value of TERM cannot be used (e.g. in a
+chroot with missing terminfo). Note that having a built tree may cause
+surprising/broken results for NOTMUCH_TEST_INSTALLED, so consider
+cleaning first.
+

 Writing Tests
 -------------
 The test script is written as a shell script. It is to be named as
 Writing Tests
 -------------
 The test script is written as a shell script. It is to be named as