From: Eli Zaretskii <eliz@gnu.org>
To: "Harald Jörg" <haj@posteo.de>
Cc: stefankangas@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Perl and Emacs: Developing tests for progmodes
Date: Thu, 03 Sep 2020 20:34:15 +0300 [thread overview]
Message-ID: <83h7sevk6g.fsf@gnu.org> (raw)
In-Reply-To: <935d77f8-72c4-16fd-f9d6-39ba965e99e8@posteo.de> (message from Harald Jörg on Thu, 3 Sep 2020 15:42:47 +0200)
> From: Harald Jörg <haj@posteo.de>
> Date: Thu, 3 Sep 2020 15:42:47 +0200
> Cc: Stefan Kangas <stefankangas@gmail.com>,
> Stefan Monnier <monnier@iro.umontreal.ca>
>
> To solve this, we could:
>
> - Split the tests into two and manually copy over tests where this
> makes sense or:
>
> - Split the tests into a "common" set plus two sets for the specific
> modes (how would the files be named in that case?) or:
>
> - Keep all tests in one file and tag the individual tests.
>
> Are there any similar cases in the set of Emacs packages, or
> conventions how to do it?
Don't perl-mode and cperl-mode live on 2 separate files? We generally
have a structure under test/ that mirrors the file hierarchy of the
sources being tested, so it would be natural to have 2 separate files,
test/lisp/progmodes/perl-mode-tests.el and
test/lisp/progmodes/cperl-mode-tests.el.
Does that answer your question?
next prev parent reply other threads:[~2020-09-03 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:42 Perl and Emacs: Developing tests for progmodes Harald Jörg
2020-09-03 15:52 ` Stefan Monnier
2020-09-03 20:17 ` Stefan Kangas
2020-10-22 13:42 ` Stefan Kangas
2020-10-22 15:28 ` Stefan Monnier
2020-10-22 16:32 ` Stefan Kangas
2020-10-22 16:30 ` Harald Jörg
2020-10-22 19:38 ` Stefan Kangas
2020-09-03 17:34 ` Eli Zaretskii [this message]
2020-09-03 20:00 ` Harald Jörg
2020-09-04 6:55 ` Eli Zaretskii
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=83h7sevk6g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=haj@posteo.de \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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).