From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Gnus automatic builds
Date: Thu, 07 Apr 2011 22:02:36 +0200 [thread overview]
Message-ID: <87ipup25k3.fsf@randomsample.de> (raw)
In-Reply-To: <87ipuprgat.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 07 Apr 2011 14:51:22 -0500")
Ted Zlatanov writes:
> On Thu, 07 Apr 2011 21:21:46 +0200 David Engster <deng@randomsample.de> wrote:
>
> DE> Problem is: ERT does not run under Emacs 22, nor under XEmacs. So only
> DE> Emacs 23 and 24 will currently run the tests. Maybe someone will port
> DE> ERT to XEmacs, then we can add that any time.
>
> I guess we could bundle ERT with the Gnus tests. I was hoping to avoid
> that. Can it be installed in XEmacs as a package?
No, ERT simply won't run under Emacs22 and XEmacs, so bundling won't
help (I already locally installed it for Emacs23 on the server). Emacs22
is missing 'special-mode', as does XEmacs. Additionally, ERT is using
the 'button' library, which apparently isn't available for XEmacs. At
least that's what I got from a short test; there's probably more. If
someone ports ERT to those Emacsen, I'll happily install it...
> That's reasonable. We could also run a fake NNTP server on a local port
> that knows only a few commands and send back replies for them, so the
> interaction is scripted. This approach will definitely help us find
> Gnus issues quickly. I don't like test-driven development, but once the
> code has been written, it's extremely useful to write tests too.
Yeah well, if someone writes such a server... until now, I think Gmane
will do (it's superstable, as far as I know).
As for testing nnimap, the server is running dovecot. It would be no
problem to install a test user there.
-David
next prev parent reply other threads:[~2011-04-07 20:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 4:28 no gnus registry new dependency on ert? Eric Abrahamsen
2011-04-06 10:03 ` Ted Zlatanov
2011-04-06 10:10 ` David Engster
2011-04-06 10:54 ` Ted Zlatanov
2011-04-06 13:10 ` Ted Zlatanov
2011-04-06 13:28 ` David Engster
2011-04-06 14:26 ` Ted Zlatanov
2011-04-06 14:57 ` David Engster
2011-04-06 15:00 ` Ted Zlatanov
2011-04-06 15:03 ` David Engster
2011-04-06 15:51 ` Ted Zlatanov
2011-04-06 13:15 ` Gnus automatic builds (was: no gnus registry new dependency on ert?) Ted Zlatanov
2011-04-06 13:31 ` Gnus automatic builds David Engster
2011-04-06 16:14 ` David Engster
2011-04-06 16:30 ` Ted Zlatanov
2011-04-06 18:10 ` David Engster
2011-04-06 18:57 ` Ted Zlatanov
2011-04-07 19:21 ` David Engster
2011-04-07 19:51 ` Ted Zlatanov
2011-04-07 20:02 ` David Engster [this message]
2011-04-07 21:19 ` Ted Zlatanov
2011-04-12 16:08 ` Lars Magne Ingebrigtsen
2011-04-12 16:29 ` David Engster
2011-04-12 16:36 ` Lars Magne Ingebrigtsen
2011-04-12 18:33 ` Jason L Tibbitts III
2011-04-12 18:41 ` Lars Magne Ingebrigtsen
2011-04-12 19:35 ` Jason L Tibbitts III
2011-04-12 19:46 ` David Engster
2011-04-12 19:51 ` Jason L Tibbitts III
2011-04-16 8:22 ` David Engster
2011-04-16 15:19 ` Ted Zlatanov
2011-04-20 18:50 ` David Engster
2011-04-20 20:58 ` Ted Zlatanov
2011-04-22 11:27 ` Adam Sjøgren
2011-04-22 21:21 ` David Engster
2011-04-25 9:05 ` Adam Sjøgren
2011-04-12 20:00 ` Lars Magne Ingebrigtsen
2011-04-20 20:59 ` David Engster
2011-04-20 21:03 ` Ted Zlatanov
2011-04-20 21:31 ` Jason L Tibbitts III
2011-04-21 7:33 ` David Engster
2011-04-25 12:28 ` Ted Zlatanov
2011-04-06 20:26 ` David Engster
2011-04-07 19:30 ` David Engster
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipup25k3.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).