[Systers-dev] New Testing Cycle - ORM project

[Robin Jeffries]

All it takes to test is a moderate knowledge of mailman.  If there are test
cases that you don't understand how to exercise, we are quite happy to
explain them to you.  The point of this list is to get folks involved in
this development project, and the easiest, least background knowledge way to
do this is to engage in the testing.  If you are trying to get back to a
technical roll, this seems like a really low stress first step, where very
little can go wrong -- this is a woman friendly list, and no one is going to
flame you if you get a test wrong or don't understand the instructions
(though we might ask you to edit the instructions to make them clearer).
Seriously, if you joined this list to get involved in the systers project in
any way, and if you have an hour in the next 2 days or so, contributing to
the testing is going to make you feel competent and successful -- I promise
you that.

If you have questions, ask them on this list so that others can benefit.

Jen, I think the first step needs to be to create a list that can be used by
all the tests that assume a list exists.  Can you or Kanika Vats create that
list, tell the rest of us it's name/url (so we don't have half a dozen lists
created and stepping on each others toes). and let us know the management
password for that list.

BTW, now that the testing is done for the last set, I'm going to change the
management password for it, so that we don't have an ongoing security hole.

Robin

On Tue, Jul 28, 2009 at 4:09 PM, Jennifer Redman <jenred at gmail.com> wrote:

> Our first testing cycle was completed successfully and the bug fix for Bug
> #344387 <https://bugs.launchpad.net/systers/+bug/344387> is queued up and
> ready to be rolled to production (Thanks Anna!)
> The new ORM feature branch is now on abiwt.org and ready for testing.
>
> The testing checklist may be found here:
>
>
> http://systers.org/systers-dev/doku.php/checklist_for_27_july_2009_-_orm_release_1.0
>
> Kanika Vats - I'm going to let you lead the testing effort, Annie Lee has
> some availability, Anna has offered to help and Malveeka will hopefully
> pitch in since she is waiting for her code to get rolled out.
>
> Additionally, we are always looking for additional help testing!  Feel free
> to email me if you have some time this week to help test.
>
> Because this is a new feature please associate the ORM branch with any bugs
> filed and assign Kanika-Vats the bug.
>
> Choose "Link a Related Branch" and then enter
> ~systers-dev/systers/orm<
> https://bugs.launchpad.net/systers/+bug/301431/@@popup-window?search=systers-dev&vocabulary=Branch&field=field.branch#
> >
> -
> to associate the branch.
>
> File bugs here:
>
> https://bugs.launchpad.net/systers
>
> We'd like to move through this testing cycle fairly quickly so we can begin
> testing Malveeks sql membership adaptor on Thursday.
>
> Let me know if anyone has any questions,
>
> Thanks,
> Jen
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testingorm+unsubscribe at systers.org<systers-dev%2Btestingorm%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=27&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testingorm at systers.org <systers-dev%2Btestingorm 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.
>