<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>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.<BR><BR>
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.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Tue, 26 Aug 2008 12:02:58 -0400<BR>> From: sdague@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] (proposal) QA, Release and other tought<BR>> <BR>> Lc wrote:<BR>> > yes but no automatic test will find any inventory or assets issues or other<BR>> > wearable prims lost in the metagrid...<BR>> <BR>> Um, I'm not sure how you can say that. If you can figure that out, so<BR>> can a computer. :)<BR>> <BR>> The existing bamboo stuff is just unit tests on the code. Those are<BR>> important, but don't really test anything with state.<BR>> <BR>> At some point we'll get to state testing that will do things like login,<BR>> and look at stuff (using libopenmv). That sort of approach works much<BR>> better than trying to get people to go through a spreadsheet.<BR>> <BR>> -Sean<BR>> <BR>> -- <BR>> Sean Dague / Neas Bade<BR>> sdague@gmail.com<BR>> http://dague.net<BR>> <BR>> <BR><BR></body>
</html>