From 2a24aac12e4c792acc5fb1f7a121dcdfbf086e01 Mon Sep 17 00:00:00 2001 From: Stephen Morris Date: Fri, 26 Jan 2018 19:40:12 +0000 Subject: [PATCH] [rt46602] Mention conf.sh.win32 in instructions for adding a test. (cherry picked from commit 23dfa27a84f6c724853fcad3f4a0222e2b02fd1f) (cherry picked from commit 06a9a37d3b7e710d739d906ae1aff3942bb7ccea) (cherry picked from commit d9740c20da9f8451882d5d8d12139bd1b91af544) --- bin/tests/system/README | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/bin/tests/system/README b/bin/tests/system/README index 15a0115a2d2..9d81499c529 100644 --- 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 -- 2.47.3