From c992dca26e2b7d02ec7d43f2b71ff23d77e39f27 Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Tue, 19 Jun 2018 19:30:50 -0400
Subject: 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.
---
 src/test/recovery/README | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

(limited to 'src/test/recovery')

diff --git a/src/test/recovery/README b/src/test/recovery/README
index 93bdcf4fed6..a1e1aa1be1c 100644
--- a/src/test/recovery/README
+++ b/src/test/recovery/README
@@ -8,14 +8,16 @@ This directory contains a test suite for recovery and replication.
 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 some tests may create one or multiple nodes, be they master or
-standby(s) for the purpose of the tests.
-
-NOTE: This requires the --enable-tap-tests argument to configure.
+Either way, this test initializes, starts, and stops several test Postgres
+clusters.
-- 
cgit v1.2.3