Hi All On 12 Jan 2011, at 09:12, Scott Wilson wrote:
> > On 17 Dec 2010, at 16:08, Ross Gardler wrote: > >> On 17/12/2010 15:48, Scott Wilson wrote: >>> On 17 Dec 2010, at 15:17, Kris Popat wrote: >>> >>>> On 17 Dec 2010, at 14:50, Ross Gardler wrote: >>>> >>>>> On 17/12/2010 14:32, Kris Popat wrote: >>>>> >>>>> Lets go with Scotts suggestion to distribute a WAR alongside a >>>>> binary. The standalone version is only to make it easy for >>>>> developers so there is no need to worry about a binary of that. >>>>> >>>> >>>> Okay I'll create and test a war with Tomcat, what other application >>>> servers should we test against? >>> >>> I think just testing against a couple of versions of Tomcat (6, 7) >>> should be enough for now, we can always put a note with the WAR to >>> that effect. I have come up against a persistence issue with the WAR file. This can be made to work under tomcat using mysql. As I understand it having a dependency on mysql is a licensing problem. I'm just working out how that dependency can be unpicked. However if anyone knows how this can be done (or if there is a simple way to build the WAR file so it will work with derby out of the box) just to save me going round the houses that would be great. >> >> The testing is done by the community. Create a release candidate and make it >> available. Ask our community to test in any environment they have available >> to them and submit the results to an issue. >> >> We should really have a set of test scripts (as in human readable things) >> that test at least the critical paths in the system. Here's a starter: > > > I've put the script up on the Wiki and made a few edits: > > https://cwiki.apache.org/confluence/display/WOOKIE/Testing+a+Release > > (Note that testing service types is still TODO) > >> >> Testing >> ======= >> >> Ideally the client will access from a different network machine to the >> server. >> >> - deploy the war and check index page responds >> >> Widget Gallery >> ============== >> >> - open a new browser window on the server home page >> >> - click view widget gallery >> >> - pick a random widget and click "Demo" >> >> - ensure the widget behaves as expected >> >> - refresh the page >> >> - ensure the widget behaves as expected >> >> - repeat above for at least one other widget (more is better) >> >> Administration >> ============== >> >> Widget Deployment >> ----------------- >> >> - open a new browser window on the server home page >> >> - click "Administration menu" >> >> - enter username and password (default is java, java) >> >> - click "View existing widgets" >> >> - expand random widgets and ensure page behaves as expected >> >> - click back button >> >> - click "add new widget" >> >> - upload the test widget (we should provide a simple test widget in SVN that >> is packaged but not bundled with the release - need only be a hello world at >> this stage) >> >> - repeat the "Widget Gallery" tests above with the test widget >> >> Gadget Deployment >> ----------------- >> >> - Repeat the Widget Deployment above but with a Gadget rather than a Widget >> >> Remove Widget >> ------------- >> >> - Click "Remove widget" >> >> - find the test widget and delete it >> >> - check widget is not available in widget gallery >> >> Service Types >> ------------- >> >> How do we test this? >> >> White List >> ---------- >> >> - Click White List >> >> Access request policies >> ----------------------- >> >> - Click "Manage widget access request policies" >> >> - revoke policies for weather widget >> >> - Check Weather widget does not work via the gallery (note it silently fails >> at present) >> >> - add http://feeds.bbc.co.uk to the whitelist >> >> - Check weather widget works via widget gallery >> >> Instantiation >> ============= >> >> - go back to the index page (Other - back to main menu) >> >> - click "instantiate a widget" >> >> - select a random widget in "Service Type" >> >> - click submit >> >> - copy URL from returned XML document >> >> - enter URL into browser >> >> - check widget works OK >> >> Reporting >> ========= >> >> Thanks for testing. Please be sure to report your successes and failures in >> the issue XXXXXXXX. Please include: >> >> Server OS: >> Client OS: >> Server and Client separate machines?: >> Servlet Engine: >> Java version: >> Browser: >> Browser version: >> >> Ross >
