; * CONTRIBUTE: Suggest to run more tests sometimes.

(cherry picked from commit 05ee2b741f074b64c46a1063ec331e111099fc31)

diff --git a/CONTRIBUTE b/CONTRIBUTE
index 0465bdee9fc89a9e119f876e91f6711e62235fa2..0ab45a99ee28dcc585cf5b6f6cd6093160493ef3 100644 (file)
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -178,6 +178,19 @@ tests via
 
     make && make -C test xt-mouse-tests
 
+Changes in code that implements infrastructure capabilities might affect
+many tests in the test suite, not just the tests for the source files
+you changed.  For such changes, we recommend running unit tests that
+invoke the functions you have changed.  You can search for the tests
+that might be affected using tools like Grep.  For example, suppose you
+make a change in the 'rename-file' primitive.  Then
+
+  grep -Rl rename-file test --include="*.el"
+
+will show all the unit tests which invoke rename-file; run them all to
+be sure your changes didn't break the test suite.  If in doubt, run the
+entire suite.
+
 ** Commit messages
 
 Ordinarily, a changeset you commit should contain a description of the