guix_mirror_bot pushed a commit to branch emacs-team
in repository guix.

commit c304a3b7a3d3ee6e9492a5a14e40ab9c0ed48df1
Author: Morgan Smith <[email protected]>
AuthorDate: Thu Sep 4 12:06:32 2025 -0400

    doc: Emacs Packages: Remove outdated commentary on testing.
    
    * doc/contributing.texi (Emacs Packages): Remove outdated commentary on
    testing.  We now run the tests by default like is done in other build 
systems.
    
    Signed-off-by: Liliana Marie Prikler <[email protected]>
---
 doc/contributing.texi | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 7e5b9d77a4..71be4f3338 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1566,14 +1566,7 @@ collection has no regressions and can still be built 
successfully:
 Emacs packages should preferably use the Emacs build system
 (@pxref{emacs-build-system}), for uniformity and the benefits provided
 by its build phases, such as the auto-generation of the autoloads file
-and the byte compilation of the sources.  Because there is no
-standardized way to run a test suite for Emacs packages, tests are
-disabled by default.  When a test suite is available, it should be
-enabled by setting the @code{#:tests?} argument to @code{#true}.  By
-default, the command to run the test is @command{make check}, but any
-command can be specified via the @code{#:test-command} argument.  The
-@code{#:test-command} argument expects a list containing a command and
-its arguments, to be invoked during the @code{check} phase.
+and the byte compilation of the sources.
 
 The Elisp dependencies of Emacs packages are typically provided as
 @code{propagated-inputs} when required at run time.  As for other

Reply via email to