From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, Philipp <p.stephani2@gmail.com>,
51941@debbugs.gnu.org
Subject: bug#51941: Detect duplication of ERT tests
Date: Fri, 19 Nov 2021 10:33:42 +0100 [thread overview]
Message-ID: <1EA3587F-ED28-48F1-B149-0E78B662D5CC@acm.org> (raw)
In-Reply-To: <87y25kyars.fsf@gnus.org>
19 nov. 2021 kl. 06.28 skrev Lars Ingebrigtsen <larsi@gnus.org>:
>> Seems to me that making "should" only be defined within tests would have
>> flagged these (https://debbugs.gnu.org/28385).
>
> But like I said there, using `should' outside tests is really convenient
> when developing.
You are both right -- apart from the development convenience, functions form an important abstraction mechanism in Lisp and they can be valuable for decomposing test code (although I don't think I've ever done so myself). On the other hand, disallowing them outside `ert-deftest` might help eliminate the mistakes that we are talking about.
A quick scan finds 365 occurrences of `should`, `should-not` and `should-error` inside defuns in the test/ subtree.
next prev parent reply other threads:[~2021-11-19 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:16 bug#51941: Detect duplication of ERT tests Mattias Engdegård
2021-11-18 10:35 ` Lars Ingebrigtsen
2021-11-18 11:54 ` Mattias Engdegård
2021-11-18 11:58 ` Lars Ingebrigtsen
2021-11-18 17:44 ` Lars Ingebrigtsen
2021-11-18 17:53 ` Philipp Stephani
2021-11-18 19:13 ` Mattias Engdegård
2021-11-18 19:34 ` Lars Ingebrigtsen
2021-11-18 19:43 ` Mattias Engdegård
2021-11-18 22:51 ` Glenn Morris
2021-11-19 5:28 ` Lars Ingebrigtsen
2021-11-19 9:33 ` Mattias Engdegård [this message]
2021-11-20 8:38 ` Lars Ingebrigtsen
2021-11-20 8:49 ` Mattias Engdegård
2021-11-24 7:30 ` Ihor Radchenko
2021-11-24 8:52 ` Mattias Engdegård
2021-11-24 9:29 ` Ihor Radchenko
2021-11-24 10:00 ` Mattias Engdegård
2021-11-24 12:16 ` Ihor Radchenko
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=1EA3587F-ED28-48F1-B149-0E78B662D5CC@acm.org \
--to=mattiase@acm.org \
--cc=51941@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--cc=rgm@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).