From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] test: Add tests for advance/rewind.
In-Reply-To: <cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net>
References: <1324665712-2419-1-git-send-email-dme@dme.org>
	<1325160490-23472-1-git-send-email-dme@dme.org>
	<1325160490-23472-2-git-send-email-dme@dme.org>
	<cunmxabqs6k.fsf@hotblack-desiato.hh.sledj.net>
User-Agent: Notmuch/0.10.2+138~g0b4049e (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Fri, 06 Jan 2012 09:10:17 -0800
Message-ID: <874nw83gg5.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: list

--=-=-=

On Thu, 29 Dec 2011 16:05:39 +0000, David Edmondson <dme@dme.org> wrote:
> 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.)

I think it's a nice idea.  It seems much cleaner than writing ever more
complicated code in the command line.  There was another recent idea to
actually write the python tests in python, if I remember correctly.  It
all seems to make sense to me.  Bash is convenient, but there's no
reason we need to be monogamous, especially when there are ways, with
your technique, to call individual "embedded" tests from the command
line and still take advantage of the bells and whistles of full test
infrastructure.

> 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').

It is really nice to see diffs on failure, actually, to get a sense of
what exactly went wrong.  Is it possible to have some sort of standard
report to stdout that could provide more info?

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJPByr6AAoJEO00zqvie6q8xugQAI48tXtAU0fFNeuJDC6YmIIi
F2mGihoAW9vD9dQRH+Vjiv6ef34GgPThuk/Qf5fSPbTBkr3SF6XK8wTXUYxIpEXe
RxzttX1OKcFnRM3MLe+cmJL1K+23vkeQcrux0b1YjWYwffpcbGPsOzzS6+grv8fQ
opHStOHrxEUzbF1F5sdLKW1c0bqVNUfXP3VMefw8QCyPxhik9yvGiAbWjk5pZZrN
9vc8Im6V0y95QYG1SvMp5+CbdKduKqGArdVOAJFFEHjEbxjP+/fvqDIna4deEgNb
1ksupaHd1m2BgR+jQ9NqKpge+SWW0oB/76I6x6axiidX/UCm+JLJUe1SKbT2MiVQ
apGFFP65QbIr7GO+EkwNdeszgX47M4WnHPN6/d6/DC/rhqDAwDRGgSr+C7dYXnhu
UUcI86XNYfGRhVnok0/hxQQI1+VPrdC6kMkQfAwCr8yeaLpOXT+VGYr4VnI6n6B0
di8EMMAUwHfPd0q7aVj1SMtkZM9jAujtA4KxcFtdoAEuKssaOkuvVLH1rAzwT5Wd
/tVSmHr+ajS3lrFxbLKrPDAdqluygmz6bzSkHUiF18GM+SdZ50MhPiuObzin2Pxu
Tqw1uenOmA46kW2tEaYOuWbvEJ93j3qzlKEZh2FSu8glQ/+UxgZcZsA4COgala03
J5SsvYtAIR8It1lC6py/
=xCDc
-----END PGP SIGNATURE-----
--=-=-=--