[Opensim-dev] (proposal) QA, Release and other tought

[Stefan Andersson]

Actually, what you _can_ do is to create a test harness that tests all your logic assumptions - but environmental issues like timeouts et c is an entirely different beast; these are run in integrations tests, and at the moment will probably hamper dev more than help production.
Still, even if you can't unit-test all different request response times, you can still test what the system will do if it gets an timeout or an invalid response. It's just a matter of refactoring decoupling and indirection.
Best regards,Stefan AnderssonTribal Media AB Join the 3d web revolution : http://tribalnet.se/ 



> Date: Tue, 26 Aug 2008 12:02:58 -0400> From: sdague at gmail.com> To: opensim-dev at lists.berlios.de> Subject: Re: [Opensim-dev] (proposal) QA, Release and other tought> > Lc wrote:> > yes but no automatic test will find any inventory or assets issues or other> > wearable prims lost in the metagrid...> > Um, I'm not sure how you can say that. If you can figure that out, so> can a computer. :)> > The existing bamboo stuff is just unit tests on the code. Those are> important, but don't really test anything with state.> > At some point we'll get to state testing that will do things like login,> and look at stuff (using libopenmv). That sort of approach works much> better than trying to get people to go through a spreadsheet.> > -Sean> > -- > Sean Dague / Neas Bade> sdague at gmail.com> http://dague.net> > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080826/e5783e4b/attachment-0001.html>