From: Eli Zaretskii <eliz@gnu.org>
To: Xiyue Deng <manphiz@gmail.com>
Cc: mattiase@acm.org, 66782@debbugs.gnu.org
Subject: bug#66782: 29.1; ERT tests report test redefined depending on loading sequence
Date: Sat, 28 Oct 2023 14:34:53 +0300 [thread overview]
Message-ID: <83jzr7c74y.fsf@gnu.org> (raw)
In-Reply-To: <87jzr7gfso.fsf@debian-hx90.lan> (message from Xiyue Deng on Sat, 28 Oct 2023 04:14:15 -0700)
> From: Xiyue Deng <manphiz@gmail.com>
> Cc: mattiase@acm.org, 66782@debbugs.gnu.org
> Date: Sat, 28 Oct 2023 04:14:15 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > OK, but why do that in a single Emacs session? That is unclean for
> > much more important reasons: some left-overs from previous tests could
> > affect the following tests. IMO, each test should be run in a fresh
> > Emacs session, i.e. no command line should ever load more than a
> > single test file.
>
> I think one reason is that doing all test in one session gives you a
> nice summary of how many tests passed and which ones failed in the end.
> If you run just one test per session you'll have to inspect the results
> manually which could be much more time consuming for large test suites,
> and plus it may be slower.
The usual way of doing this is to generate summary by some shell
script, which runs all the tests one by one. Emacs is not the only
program that can count ;-)
next prev parent reply other threads:[~2023-10-28 11:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:59 bug#66782: 29.1; ERT tests reports test redefined depending on loading sequence Xiyue Deng
2023-10-28 6:32 ` Eli Zaretskii
2023-10-28 9:39 ` bug#66782: 29.1; ERT tests report " Xiyue Deng
2023-10-28 9:48 ` Eli Zaretskii
2023-10-28 11:14 ` Xiyue Deng
2023-10-28 11:34 ` Eli Zaretskii [this message]
2023-10-28 11:50 ` Xiyue Deng
2023-10-28 12:03 ` Eli Zaretskii
2023-10-28 12:46 ` Mattias Engdegård
2023-10-28 21:19 ` Xiyue Deng
2023-10-29 12:09 ` Mattias Engdegård
2023-10-29 21:53 ` Xiyue Deng
2023-10-30 12:04 ` Mattias Engdegård
2023-10-30 20:47 ` Xiyue Deng
2023-11-02 17:17 ` Xiyue Deng
2023-11-02 18:56 ` Mattias Engdegård
2023-11-02 22:00 ` Xiyue Deng
2023-11-03 17:14 ` Mattias Engdegård
2023-11-03 17:56 ` Xiyue Deng
2023-11-04 8:51 ` Eli Zaretskii
2023-10-28 19:41 ` Xiyue Deng
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=83jzr7c74y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66782@debbugs.gnu.org \
--cc=manphiz@gmail.com \
--cc=mattiase@acm.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).