From: David Edmondson <dme@dme.org>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test: Add tests for advance/rewind.
Date: Thu, 29 Dec 2011 16:05:39 +0000 [thread overview]
Message-ID: <cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net> (raw)
In-Reply-To: <1325160490-23472-2-git-send-email-dme@dme.org>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
What's the general feeling about this approach to producing tests for
the emacs UI? (That is, code the test in a .el file and call the
relevant function(s) from the test harness.)
It makes it simpler to develop and maintain the test (because you can do
more work with traditional emacs support for editing elisp), but might
make interpreting failures more difficult (the test harness mostly just
reports 'failed').
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-12-29 16:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:"1324553312-10972-1-git-send-email-dme@dme.org">
2011-12-23 18:41 ` [RFC][PATCH v4] emacs: Re-implement advance/rewind functions of notmuch-show-mode David Edmondson
2011-12-23 19:01 ` Dmitry Kurochkin
2011-12-26 10:46 ` David Edmondson
2011-12-26 11:09 ` Dmitry Kurochkin
2011-12-26 22:00 ` David Edmondson
2011-12-26 22:24 ` Jameson Graef Rollins
2011-12-27 7:56 ` David Edmondson
2011-12-25 1:06 ` Austin Clements
2011-12-26 4:11 ` Aaron Ecay
2011-12-26 10:54 ` David Edmondson
2011-12-26 10:49 ` David Edmondson
2011-12-28 15:22 ` David Edmondson
2011-12-28 18:04 ` Aaron Ecay
2011-12-28 20:21 ` Jameson Graef Rollins
2011-12-29 8:42 ` David Edmondson
2011-12-29 12:08 ` [PATCH 1/2] " David Edmondson
2011-12-29 12:08 ` [PATCH 2/2] test: Add tests for advance/rewind David Edmondson
2011-12-29 16:05 ` David Edmondson [this message]
2012-01-06 17:10 ` Jameson Graef Rollins
2012-01-06 17:31 ` David Edmondson
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net \
--to=dme@dme.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).