From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: tagging ERT tests with bug numbers
Date: Fri, 04 Aug 2017 09:22:26 +0200 [thread overview]
Message-ID: <87tw1nn6fh.fsf@detlef> (raw)
In-Reply-To: <8760e4bfrn.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 03 Aug 2017 15:41:32 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> I think it would be terrific if we could tag ERT tests with the bug ID
> and URL, so these could be shown automatically if the test failed.
>
> Is there a way to do that? I know we can put properties onto symbols,
> but maybe there's a way to tag ERT tests in particular? I don't see
> anything in the docs besides predicates, which these tags are not.
ERT tests have the :tags list. We use it for example like
:tags '(:expensive-test)
AFAIK, there are no restrictions on tags, so we could define our
own. Something like
:tags '((:bug <nnn>))
And a helper function to show the bug, either via a url (derived from
the bug number), or a debbugs-gnu function.
> Thanks
> Ted
Best regards, Michael.
next prev parent reply other threads:[~2017-08-04 7:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 15:50 Question about test failure on Hydra Stephen Berman
2017-07-30 15:59 ` Eli Zaretskii
2017-07-30 20:23 ` Stephen Berman
2017-07-31 3:26 ` Eli Zaretskii
2017-07-31 9:20 ` Stephen Berman
2017-08-01 3:12 ` Eli Zaretskii
2017-08-01 9:57 ` Stephen Berman
2017-08-01 13:49 ` Eli Zaretskii
2017-08-01 15:23 ` Stephen Berman
2017-08-02 15:27 ` Stephen Berman
2017-08-01 4:39 ` Tino Calancha
2017-08-01 9:57 ` Stephen Berman
2017-08-01 10:17 ` Tino Calancha
2017-08-01 10:47 ` Stephen Berman
2017-08-05 13:07 ` Tino Calancha
2017-08-05 21:34 ` Stephen Berman
2017-08-03 19:41 ` tagging ERT tests with bug numbers (was: Question about test failure on Hydra) Ted Zlatanov
2017-08-04 7:22 ` Michael Albinus [this message]
2017-08-04 13:28 ` tagging ERT tests with bug numbers Ted Zlatanov
2017-08-04 14:50 ` Michael Albinus
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=87tw1nn6fh.fsf@detlef \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@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).