Thanks for leading on this, Gabriel. Two things that come to mind:
* Map opening, copying, metadata editing, saving. I think the parts of the app that have to do with keeping the Map Composer and the Django web app interfaces in sync are sensitive. * I think internationalization is something we are going to need to be on look out for a lot. I think the best way of testing this is going to be to actually complete the Spanish dictionary file for the site, but the bugs here are going to include both untranslated strings in the source code and also problems with the mechanism for switching site languages. On Mon, Aug 2, 2010 at 12:11 PM, Gabriel Roldan <[email protected]> wrote: > Hi all, > > > talking with Seb we thought it would be a good idea to have a release > test plan, so I'm stepping up to write the script and give it a run. > > Now, I don't know what you all think about having a formal QA plan for > GeoNode, I think it would be a good idea and that a release test script > would be a good start. > > If at all, we can get something good for the beta and get it more solid > for the 1.0 release. > > It would be extremely helpful if you tell me which aspects of the system > you think would make the most sense to be in there. Have you been > working on some functionality you would like to be sure it's working by > the time we release? can you think of any specific workflow/use cases > that we should deliver sure they work? Please tell and I'll try to get > them covered. > > Meanwhile I'll be doing some little research on how these kind of > scripts can efficiently be developed and followed. > > All comments are appreciated. > > Best regards, > Gabriel > > -- > Gabriel Roldan > OpenGeo - http://opengeo.org > Expert service straight from the developers. > -- Sebastian Benthall OpenGeo - http://opengeo.org
