From bb6d189523211486cff674b6ed4d5cc2a11b8514 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Tue, 28 Jan 2025 16:57:47 +0200 Subject: [PATCH] ; * CONTRIBUTE: Suggest to run more tests sometimes. (cherry picked from commit 05ee2b741f074b64c46a1063ec331e111099fc31) --- CONTRIBUTE | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CONTRIBUTE b/CONTRIBUTE index 0465bdee9fc..0ab45a99ee2 100644 --- 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 -- 2.39.5