[Systers-dev] GSoC Test Cycles 3 and 4

[Robin Jeffries]

My take is that all admin tasks and the core sending/receiving/replying
tasks should be tested on a dlist and a non-dlist list.  Subscription and
unsubscription actions should be tested on an essay and a non-essay list.
 There may be other things that we need to test in multiple situations, but
they don't occur to me right now.
Robin

On Tue, Aug 11, 2009 at 7:17 AM, Anna Granudd <anna.granudd at gmail.com>wrote:

> Hi,
>
> On Tue, Aug 11, 2009 at 4:05 PM, Jenred <jenred at gmail.com> wrote:
>
> > On Aug 11, 2009, at 2:15, Anna Granudd <anna.granudd at gmail.com> wrote:
> >
> >  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?
> >>
> >
> > You can always ssh into abiwt and check the log (bzr log) and then do a
> > couple # less <filename> on files you know you've changed.
> >
> >
> >  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.
> >>
> >
> > What do you think is the best approach?
> >
> >  Jen
>
>
> I don't think it's necessary to run all tests twice (or more) due to every
> change or bug fix, but I do think we should test the most important things
> for non dlists as well, not just dlists. This due to the one bug that only
> allowed us to really create dlists earlier. So far (today) I only tested
> things for dlists on abiwt.org, indicating that much of what's left is
> that
> we'll need to run tests on non dlists. I could add some things to test to
> the checklist and after that - could you please say if it's enough/too
> much?
>
> Thanks,
> Anna
>
>
> 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.
>