From barry at python.org  Sat May  1 11:39:52 2004
From: barry at python.org (Barry Warsaw)
Date: Sat May  1 11:39:59 2004
Subject: [Mailman3-dev] added interface to subscription
In-Reply-To: <A5504EEE-9B20-11D8-B87E-000A95AB83D2@digitalcommute.com>
References: <A5504EEE-9B20-11D8-B87E-000A95AB83D2@digitalcommute.com>
Message-ID: <1083425992.3975.208.camel@anthem.wooz.org>

On Fri, 2004-04-30 at 23:35, Michael Kato wrote:
> I've added the interface to subscriptions.  I also have been reworking 
> the tests to work better with test.py.  Most of the tests that are 
> valid are now working with both backends.  

Excellent, thanks Maki.

> To test the berkley backend, 
> the bakendtest.conf needs to look like:
> 
> <databases>
>      <bdblist>
>          path $vardir/listdb
>      </bdblist>
> 
>      <bdbuser>
>          path $vardir/userdb
>      </bdbuser>
> 
>      storage lists bdblist
>      storage users bdbuser
> #    <stubuser/>
> #    <stublist/>
> 
> #    storage lists stublist
> #    storage users stubuser
> </databases>
> 
> Maybe soon I'll get around to fixing the test.py to take a conf file 
> that then does the right thing.  It seems to be running by chance 
> because mailman/stubbackend/tests/test_config2.py is the first test 
> file run, and happens to load a config that is then reused.  I just 
> discovered this and thought it was funny(that test.py runs by chance)

Not funny, "ha ha", but funny "heh, we should fix that" :)

The other thing we need is a Berkeley test conf file that will point to
different databases, so they can't affect any read operational databases
that might be in place.

We probably want a different test.conf file for each backend storage
combination we want to test.  E.g. bdb-test.conf and stub-test.conf. 
Then the test infrastructure could be used to choose which one to use. 
I'm thinking that the stub backend would be the default, but you could
provide a --confs="stub bdb" or --confs="all" switch to have the
specified backends tested.

The other key point is that for unit tests, we need to arrange so that
each test is performed independently of any other test.  Probably we
should write a base test class that does the right thing in its setUp()
and tearDown() to delete any databases (or clear them out) between
tests.  It'll be much faster to do that in the stub backend.

-Barry

P.S. you're right that mailman/interface/users.py is obsolete.  I
haven't removed it yet because it provides some valuable documentation
:)



From barry at python.org  Sat May  1 13:26:28 2004
From: barry at python.org (Barry Warsaw)
Date: Sat May  1 13:26:34 2004
Subject: [Mailman3-dev] Hanging out on #mailman3
Message-ID: <1083432387.3975.220.camel@anthem.wooz.org>

Although I don't have a regular schedule for working on Mailman3, I'm
going to try as a general rule to log into irc.freenode.net #mailman3
whenever I am spending some time on it.

Feel free to come on over and chat whenever you see me there.

-Barry