[rt46602] Mention conf.sh.win32 in instructions for adding a test.

(cherry picked from commit 23dfa27a84f6c724853fcad3f4a0222e2b02fd1f)
(cherry picked from commit 06a9a37d3b7e710d739d906ae1aff3942bb7ccea)

diff --git a/bin/tests/system/README b/bin/tests/system/README
index 15a0115a2d241337e99c3b6aa7178f9732c8168a..9d81499c529b582cdf4c49ef199a2417db67f715 100644 (file)
--- a/bin/tests/system/README
+++ b/bin/tests/system/README
@@ -666,16 +666,20 @@ Adding a Test to the System Test Suite
 ---
 Once a test has been created, the following files should be edited:
 
-* conf.sh.in  The name of the test should be added to one of the the
-PARALLELDIRS or SEQUENTIALDIRS variables.  The former is used for tests that
+* conf.sh.in  The name of the test should be added to the PARALLELDIRS or
+SEQUENTIALDIRS variables as appropriate.  The former is used for tests that
 can run in parallel with other tests, the latter for tests that are unable to
 do so.
 
+* conf.sh.win32 This is the Windows equivalent of conf.sh.in.  The name of the
+test should be added to the PARALLELDIRS or SEQUENTIALDIRS variables as
+appropriate.
+
 * Makefile.in The name of the test should be added to one of the the PARALLEL
 or SEQUENTIAL variables.
 
 (It is likely that a future iteration of the system test suite will remove the
-need to edit two files to add a test.)
+need to edit multiple files to add a test.)
 
 
 Valgrind