Re: [PATCH 2/2] test: Add tests for advance/rewind.

diff --git a/33/fe912240f07ff849ffdcaf9876876edfb35329 b/33/fe912240f07ff849ffdcaf9876876edfb35329
new file mode 100644 (file)
index 0000000..3d1fc4a
--- /dev/null
+++ b/33/fe912240f07ff849ffdcaf9876876edfb35329
@@ -0,0 +1,107 @@
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 18608404775\r
+       for <notmuch@notmuchmail.org>; Fri,  6 Jan 2012 09:10:32 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id NHglbNbXmpXX for <notmuch@notmuchmail.org>;\r
+       Fri,  6 Jan 2012 09:10:31 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 82E5240476B\r
+       for <notmuch@notmuchmail.org>; Fri,  6 Jan 2012 09:10:31 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id 1A3D2328084;\r
+       Fri,  6 Jan 2012 09:10:24 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (cpe-76-174-137-84.socal.res.rr.com\r
+       [76.174.137.84]) (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 31DDE3280A9;\r
+       Fri,  6 Jan 2012 09:10:21 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id CC41B711; Fri,  6 Jan 2012 09:10:20 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH 2/2] test: Add tests for advance/rewind.\r
+In-Reply-To: <cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net>\r
+References: <1324665712-2419-1-git-send-email-dme@dme.org>\r
+       <1325160490-23472-1-git-send-email-dme@dme.org>\r
+       <1325160490-23472-2-git-send-email-dme@dme.org>\r
+       <cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net>\r
+User-Agent: Notmuch/0.10.2+138~g0b4049e (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Fri, 06 Jan 2012 09:10:17 -0800\r
+Message-ID: <874nw83gg5.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Fri, 06 Jan 2012 17:10:32 -0000\r
+\r
+--=-=-=\r
+\r
+On Thu, 29 Dec 2011 16:05:39 +0000, David Edmondson <dme@dme.org> wrote:\r
+> What's the general feeling about this approach to producing tests for\r
+> the emacs UI? (That is, code the test in a .el file and call the\r
+> relevant function(s) from the test harness.)\r
+\r
+I think it's a nice idea.  It seems much cleaner than writing ever more\r
+complicated code in the command line.  There was another recent idea to\r
+actually write the python tests in python, if I remember correctly.  It\r
+all seems to make sense to me.  Bash is convenient, but there's no\r
+reason we need to be monogamous, especially when there are ways, with\r
+your technique, to call individual "embedded" tests from the command\r
+line and still take advantage of the bells and whistles of full test\r
+infrastructure.\r
+\r
+> It makes it simpler to develop and maintain the test (because you can do\r
+> more work with traditional emacs support for editing elisp), but might\r
+> make interpreting failures more difficult (the test harness mostly just\r
+> reports 'failed').\r
+\r
+It is really nice to see diffs on failure, actually, to get a sense of\r
+what exactly went wrong.  Is it possible to have some sort of standard\r
+report to stdout that could provide more info?\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJPByr6AAoJEO00zqvie6q8xugQAI48tXtAU0fFNeuJDC6YmIIi\r
+F2mGihoAW9vD9dQRH+Vjiv6ef34GgPThuk/Qf5fSPbTBkr3SF6XK8wTXUYxIpEXe\r
+RxzttX1OKcFnRM3MLe+cmJL1K+23vkeQcrux0b1YjWYwffpcbGPsOzzS6+grv8fQ\r
+opHStOHrxEUzbF1F5sdLKW1c0bqVNUfXP3VMefw8QCyPxhik9yvGiAbWjk5pZZrN\r
+9vc8Im6V0y95QYG1SvMp5+CbdKduKqGArdVOAJFFEHjEbxjP+/fvqDIna4deEgNb\r
+1ksupaHd1m2BgR+jQ9NqKpge+SWW0oB/76I6x6axiidX/UCm+JLJUe1SKbT2MiVQ\r
+apGFFP65QbIr7GO+EkwNdeszgX47M4WnHPN6/d6/DC/rhqDAwDRGgSr+C7dYXnhu\r
+UUcI86XNYfGRhVnok0/hxQQI1+VPrdC6kMkQfAwCr8yeaLpOXT+VGYr4VnI6n6B0\r
+di8EMMAUwHfPd0q7aVj1SMtkZM9jAujtA4KxcFtdoAEuKssaOkuvVLH1rAzwT5Wd\r
+/tVSmHr+ajS3lrFxbLKrPDAdqluygmz6bzSkHUiF18GM+SdZ50MhPiuObzin2Pxu\r
+Tqw1uenOmA46kW2tEaYOuWbvEJ93j3qzlKEZh2FSu8glQ/+UxgZcZsA4COgala03\r
+J5SsvYtAIR8It1lC6py/\r
+=xCDc\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r