[Systers-dev] GSoC Test Cycles 3 and 4

[Jenred]

On Aug 11, 2009, at 7:17, 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?

Sounds like a good plan. Also make sure you are updating the bugs as  
the fix appears to pass.

Jen