[Systers-dev] GSoC Test Cycles 3 and 4

[Anna Granudd]

I'm not quite sure how to check that my changes made it through, any tips on
how to do this? Can I simply just test the features/changes I did and see if
they work or do you want me to do it somehow else?
So far I created a list called 'wishlist', password 'admin', that we can use
for testing. However some of the things implemented will require more lists
being created. I figured I could add what needs to be tested to the
checklist you created and then I'll start running tests. I'm not sure
whether to test everything on the checklist for each list we create, many of
them doesn't affect more than for instance subscription but that is up to
you Jen/Robin/Andy/Annie? to decide.

Thanks,
Anna

On Tue, Aug 11, 2009 at 8:58 AM, Jennifer Redman <jenred at gmail.com> wrote:

> Ok the wishlist branch is now on abiwt.org.  I bypassed the merge with the
> ORM branch and removed STORM for purposes of testing this branch.  Anna
> would you please double-check to make sure all your changes made it onto the
> box?  (Logs say yes -- but I had some strange issues merging your branch --
> will elaborate later.) python-markdown is installed and I started you a
> checklist on the wiki:
> http://systers.org/systers-dev/doku.php/checklist_for_wishlist_integration
> .
> There are a lot of changes in this branch -- so we need to make sure that:
>
> - For each bug fixed there needs to be a test(s) added to the template or
> someway of verifying the fix.
>
> - We really need help testing this branch.  Anna would you please create a
> test list -- and provide a password to allow volunteers to help test.
>
> Malveeka - Andy needs to do a code review on your branch changes -- he
> should be able to take a look tomorrowish.
>
> Kanika Vats - I believe you are just about done!  Congrats.  There is
> another small amount of testing with regards to your changes you made
> removing the hard-coded UID and PW, but Andy is very satisfied with your
> project (as am I).  We need to wait a bit to integrate your branch into
> stable and roll on to production -- but overall thank you for doing such an excellent job this summer.  Hopefully you have plans to stick around and continue to help out.  We need you!
>
> Thanks,
> Jen
>
>
> On Mon, Aug 10, 2009 at 10:58 AM, Anna Granudd <anna.granudd at gmail.com>wrote:
>
>> Hi,
>> for the code from the wishlist branch to work you'll need to install
>> python-markdown. I added instructions in the branch for the revision
>> containing the code and in the installation guide for setting up the dev.
>> environment, but I thought it couldn't hurt pointing it out again before
>> starting to test (not everybody might check eg. the branch before starting
>> to run tests). The package can be installed using sudo aptitude install
>> python-markdown
>>
>> Thanks,
>> Anna
>>
>> On Mon, Aug 10, 2009 at 7:06 PM, Jennifer Redman <jenred at gmail.com>wrote:
>>
>>> We coming down to the wire with regards to testing code and finishing up
>>> GSoC projects.
>>> Malveeka is working on integrating her code with the Systers MM
>>> customizations -- and should be ready for testing by Thursday or so.
>>>
>>> In the meantime, we need to work on testing Anna's wishlist branch.
>>>  There
>>> are lots of bug-fixes here.
>>>
>>> Any objections to pulling Anna's branch to abiwt.org -- tonight and then
>>> testing over the next 2 days?
>>>
>>> Kanika Vats (and Andy), we need to retest the ORM branch without the
>>> hard-coded UID and password -- is there additional code you'd like to
>>> roll-out?
>>>
>>> Also, please remember that if you introduce new dependencies -- you need
>>> to
>>> include the installation information on the wiki and in the branch.
>>>
>>> Thanks,
>>> Jen
>>>
>>>
>>> To unsubscribe from this conversation, send email to <
>>> systers-dev+cycles+unsubscribe at systers.org<systers-dev%2Bcycles%2Bunsubscribe at systers.org>>
>>> or visit <
>>> http://systers.org/mailman/options/systers-dev?override=29&preference=0>
>>> To contribute to this conversation, use your mailer's reply-all or
>>> reply-group command or send your message to
>>> systers-dev+cycles at systers.org <systers-dev%2Bcycles 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.
>>>
>>
>>
>