unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Run (some) tests more automagically?
Date: Sun, 21 Feb 2021 14:25:29 +0100	[thread overview]
Message-ID: <87v9alk0xi.fsf@gnus.org> (raw)

I wonder whether anybody's considered making "make" run some tests.

It's a recurring issue that we make a change, and then we forget to run
the test suite.  I mean, it's not a major problem, because it'll
eventually get run by somebody, but I'd feel more confident in my own
changes if I'd remember to run more tests more often.

The reason we don't is because we don't want to wait for some minutes
while running the entire suite.

So here's today's not-thought-out-at-all idea: Since tests for
lisp/foo.el live in test/lisp/foo-tests.el, could we add some Makefile
magic to automatically run foo-tests.el if lisp/foo.el has been changed?
Running just those tests shouldn't take too much time, and would
probably cover 93% of the relevant code changes for foo.el.

One disadvantage to doing this (if we find a way) is that "make
foo-tests" is often very noisy, so we'd need a way to run tests silently
and just report if anything actually fails unexpectedly, I guess.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




             reply	other threads:[~2021-02-21 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 13:25 Lars Ingebrigtsen [this message]
2021-02-21 13:48 ` Run (some) tests more automagically? dick.r.chiang
2021-02-21 14:28 ` Pip Cet
2021-02-21 14:45   ` Philipp
2021-02-21 16:05   ` Lars Ingebrigtsen
2021-02-21 15:37 ` Eli Zaretskii
2021-02-21 15:57   ` Lars Ingebrigtsen
2021-02-24 10:42 ` Phillip Lord
2021-02-24 14:34   ` Lars Ingebrigtsen
2021-02-26 11:44     ` Phillip Lord
2021-02-26 11:50       ` Lars Ingebrigtsen
2021-03-01 17:50         ` Phillip Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9alk0xi.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).