* Writing large integration tests for core Emacs
@ 2021-02-27 20:40 Matt Armstrong
0 siblings, 0 replies; only message in thread
From: Matt Armstrong @ 2021-02-27 20:40 UTC (permalink / raw)
To: Stefan Kangas, emacs-devel
Stefan Kangas <stefan@marxist.se> writes:
> Matt Armstrong <matt@rfc20.org> writes:
>
>> I did a manual test. I edited a file, then changed the file outside
>> emacs, then ran revert-buffer. The file's lock file was still removed,
>> even with the patch below applied.
>
> Perhaps we should write some automatic tests before changing anything in
> this area?
This is in-reply-to:
<CADwFkmmKSsXD20USQ=Fyvk8cXrk=+3Z+SvgUt8JEGfk+CbzsOA@mail.gmail.com>
from Steve (i.e. bug#46701) but the topic is broader than the bug.
In the context of that bug I thought about writing tests but saw little
precedent. Adding unit tests for simple functions is one thing, but in
my experience larger integration tests have a whole different cost
vs. value proposition.
Do we have other examples of tests that launch emacs as a subprocess of
itself, manipulate files outside of Emacs' knowledge, etc.?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-02-27 20:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-27 20:40 Writing large integration tests for core Emacs Matt Armstrong
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).