Re: testing Gnus and Emacs/XEmacs compatibility

[Ted Zlatanov <tzz@lifelogs.com>]

On Mon, 07 Mar 2011 18:37:15 +0100 David Engster <deng@randomsample.de> wrote: 

DE> Ted Zlatanov writes:
>> On Mon, 07 Mar 2011 08:11:19 +0100 David Engster <deng@randomsample.de> wrote: 
DE> http://www.randomsample.de/gnus-buildbot
>> Damn it, I am 90% done with mine :) 

DE> We can also migrate it to gnus.org, if you want to have it all in one
DE> place, but I also don't have a problem with hosting it.

It may be better to move the build master there so e-mails will
originate from the genuine host and get easily delivered to the right
places.  But Lars should decide.

My experience with BuildBot was pretty good, once I figured out that
when it complains on startup that package X (e.g. jinja2) is missing,
you just "apt-get install python-X".

>> Can we call yours official and be done?  Maybe we can put the tests
>> inside the Gnus repo, too?

DE> Yes to both. The tests should definitely be in the Gnus repo, preferably
DE> started with a makefile rule. I guess excluding them from the Emacs sync
DE> shouldn't be a problem?

>> I think with ERT we can do pretty well.

DE> The important thing is that the tests must be batch-mode compatible with
DE> a proper exit code. Otherwise it gets complicated... I haven't actually
DE> looked into ERT much, but since it has made its way into Emacs proper,
DE> it should be usable. :-)

I think the Emacs maintainers would love to have those tests
synchronized within Emacs.  Look at the test/ subdirectory for examples
of how they already do the testing, e.g. for CEDET.  So we can copy
their Makefiles and synchronize just the Gnus tests to work with their
testing structure.

Ted