GNU bug report logs - #66782
29.1; ERT tests reports test redefined depending on loading sequence

Previous Next

Full log

View this message in rfc822 format

From: Xiyue Deng <manphiz <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mattiase <at> acm.org, 66782 <at> debbugs.gnu.org
Subject: bug#66782: 29.1; ERT tests report test redefined depending on loading sequence
Date: Sat, 28 Oct 2023 04:14:15 -0700

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Xiyue Deng <manphiz <at> gmail.com>
>> Cc: Mattias Engdegård <mattiase <at> acm.org>,
>>   66782 <at> debbugs.gnu.org
>> Date: Sat, 28 Oct 2023 02:39:46 -0700
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > If test2 requires test1, why are both of them explicitly run from the
>> > command line?  Isn't that redundant, since running test2 will also run
>> > the tests defined by test1?
>> 
>> IIUC most projects just run all tests without explicit dependency
>> detection.  For example, in lsp-mode it uses eask ert-runner to run all
>> tests[1].
>
> 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.

-- 
Xiyue Deng

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.