Clarify the README files for the various separate TAP-based test suites.

Explain the difference between "make check" and "make installcheck".
Mention the need for --enable-tap-tests (only some of these did so
before).  Standardize their wording about how to run the tests.

1 files changed, 14 insertions, 7 deletions

diff --git a/src/test/ssl/README b/src/test/ssl/README
index 5e8bf641ba4..84baa478cef 100644
--- a/src/test/ssl/README
+++ b/src/test/ssl/README
@@ -7,20 +7,27 @@ This directory contains a test suite for SSL support. It tests both
 client-side functionality, i.e. verifying server certificates, and
 server-side functionality, i.e. certificate authorization.
 
+CAUTION: The test server run by this test is configured to listen for
+TCP connections on localhost. Any user on the same host is able to
+log in to the test server while the tests are running. Do not run this
+suite on a multi-user system where you don't trust all local users!
+
 Running the tests
 =================
 
-    make check
+NOTE: You must have given the --enable-tap-tests argument to configure.
 
+Run
+    make check
 or
-
     make installcheck
+You can use "make installcheck" if you previously did "make install".
+In that case, the code in the installation tree is tested.  With
+"make check", a temporary installation tree is built from the current
+sources and then tested.
 
-NOTE: This creates a temporary installation (in the case of "check"),
-and sets it up to listen for TCP connections on localhost. Any user on
-the same host is allowed to log in to the test installation while the
-tests are running. Do not run this suite on a multi-user system where
-you don't trust all local users!
+Either way, this test initializes, starts, and stops a test Postgres
+cluster that is accessible to other local users!
 
 Certificates
 ============