[Systers-dev] New Test Cycle - Membership Adaptor

[Malveeka Tewari]

Hey Anna

Thanks fr helping with the testing..

We need to make sure that everything is working correctly and the membership
data is getting stored into the postgre database.

I had put the instructions to check the database on the wiki.
Had also added a small point that changes be made to the database for the
relevant test cases.
Looks like I haven't done a very good job :)
Will try and fix that!

You need to ssh to abiwt.org and look into the database. and check that when
you add/remove users or change membership data the details are getting
stored to the db.

psql -d mailman_members -U mailman
password: <enter the password>
select * from mailman_test;


I have already tested that the database gets updated succesfully and
correctly when the subscriber changes membership details.
Now have to check that the changes are made to db when the admin makes
changes. (the AMM testcases)

I hope that made sense to you.
Will try making things clearer on the wiki.

Once again, thanks a lot for helping with the testing :)

Malveeka




On Thu, Aug 20, 2009 at 9:39 PM, Anna Granudd <anna.granudd at gmail.com>wrote:

> Hi,
> I did some testing on membership-dlist and membership-nodlist-noessay. I
> think those two should be enough for the listinfo part, but it's up to you
> if you think they need more testing. I couldn't log in to the admin pages so
> would you please be so kind to check that anna.granudd at gmail.com has
> digest set on both lists (I think) and anna.provar at gmail.com has it set to
> no digest? I'm not sure how to test the things implemented by you, maybe you
> could add a table with things to test specific to your changes - or have you
> already tested all that?
>
> Thanks and good luck with the rest of the tests,
> Anna
>
> On Wed, Aug 19, 2009 at 10:44 PM, Malveeka Tewari <malveeka at gmail.com>wrote:
>
>> Hi
>>
>> I have started the testing for the Membership Adaptor.
>> I have created two lists:
>> membership-dlist
>> membership-nondlist (there is another list: membership-non-dlist - do not
>> confuse between the two)
>>
>> Have updated the wiki with the tests done already and instructions to look
>> into the db.
>>
>> Thanks
>> Malveeka
>>
>>
>> On Wed, Aug 19, 2009 at 8:24 AM, Jennifer Redman <jenred at gmail.com>
>> wrote:
>>
>> > We are starting a new test cycle for the STORM Membership Adaptor.
>> > The STORM membership adaptor moves the MM membership management from the
>> > .pck files to a sql database.  We are using postgreSQL -- but ideally it
>> > should work with sqllite and mysql.  This is the middle part for
>> > integrating
>> > with OpenID.  Once this works -- we are fairly confident that
>> interfacing
>> > with an alternate authentication system should be much easier then
>> hacking
>> > directly on MM.
>> >
>> > This version of the adaptor is integrated with Systers dlist
>> functionality
>> > -- but there is another version that is stand-alone for those who may
>> not
>> > want to use dlist enabled mailman.
>> >
>> > The checklists are here:
>> >
>> >
>> >
>> http://systers.org/systers-dev/doku.php/checklist_for_30_july_2009_-_sql_membership_adaptor
>> >
>> > The test lists have been created - membership-
>> >
>> > Password is the usual (email me if you don't know and would like to
>> help).
>> >
>> > Malveeka is in charge of this test-cycle.  (Unfortunately, our students
>> in
>> > India are already back in school so additional help is appreciated.)
>> >
>> > Feel free to run a few tests!  We need your help!  If you are confused
>> --
>> > feel free to email me directly (or you can find me on chat).
>> >
>> > We also have an irc channel on irc.freenode.net #systers-dev -- I'm
>> > usually
>> > there and if you say "jenred" I'll get a color change that tells me to
>> look
>> > at that channel.  Or you can find me on gmail chat - jenred at gmail.com.
>> >
>> >
>> > Testing on this branch to run through Thursday am (PDT) at which point
>> > we'll
>> > begin our final cycle for the GSoC testing the updated ORM code
>> integrated
>> > with the new stable.
>> >
>> > We are planning a push to production on Monday evening -- if all goes
>> well.
>> >
>> > Thanks,
>> > Jen
>> >
>> >
>> > To unsubscribe from this conversation, send email to <
>> > systers-dev+membershiptes+unsubscribe at systers.org<systers-dev%2Bmembershiptes%2Bunsubscribe at systers.org>
>> <systers-dev%2Bmembershiptes%2Bunsubscribe at systers.org<systers-dev%252Bmembershiptes%252Bunsubscribe at systers.org>
>> >>
>> > or visit <
>> > http://systers.org/mailman/options/systers-dev?override=32&preference=0
>> >
>> > To contribute to this conversation, use your mailer's reply-all or
>> > reply-group command or send your message to
>> > systers-dev+membershiptes at systers.org<systers-dev%2Bmembershiptes at systers.org>
>> <systers-dev%2Bmembershiptes at systers.org<systers-dev%252Bmembershiptes at systers.org>
>> >
>> > To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
>> > >
>> > To unsubscribe entirely from systers-dev, send email to <
>> > systers-dev-request at systers.org> with subject unsubscribe.
>> >
>>
>>
>> To unsubscribe from this conversation, send email to <
>> systers-dev+membershiptes+unsubscribe at systers.org<systers-dev%2Bmembershiptes%2Bunsubscribe at systers.org>>
>> or visit <
>> http://systers.org/mailman/options/systers-dev?override=32&preference=0>
>> To contribute to this conversation, use your mailer's reply-all or
>> reply-group command or send your message to
>> systers-dev+membershiptes at systers.org<systers-dev%2Bmembershiptes at systers.org>
>> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>> >
>> To unsubscribe entirely from systers-dev, send email to <
>> systers-dev-request at systers.org> with subject unsubscribe.
>>
>
>