<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><BR>It's my understanding that we are all aiming at providing such a module repository someday.<BR>
<BR>
Now, when talking about collecting test data, one of the things I've been thinking of is an (opt-in, I guess) exception collector - ie, something that posts all exceptions (+stack traces) being thrown to a central repo, where one can sort exceptions on file, version and number of occurrences.<BR><BR>
This has worked very well in several projects I've worked with before, and becomes an invaluable tool for the debugger, to be able to browse thru various instances from various reporters, on the same exception. Also, to be able to sort the list into a top-10 severity.<BR>
<BR>
I guess there's already several existing frameworks for this (doesn't JIRA have this, for example?) - unfortunately, I've only worked with minimal and home-grown versions - but just having the collecting is a really good first step.<BR>
<BR>
I would believe that in that case, this would be a case of centralizing exception logging (something sorely needed anyway) and implement some kind of application module to interface with that exception repo?<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=EC_stopSpelling>
<BR>
Date: Sat, 30 Aug 2008 20:31:52 -0400<BR>From: imohax@gmail.com<BR>To: opensim-dev@lists.berlios.de<BR>Subject: Re: [Opensim-dev] Another idea for the OpenSimulator 0.7 roadmap - increased automated unit test / regression testing<BR><BR><BR>
<DIV dir=ltr>All that talk of user-contributed and automated testing reminds be of CPAN. I know. I know. Perl is tired old tech to some. But perhaps in the far distant future the number of OpenSim modules might approach a level where a CPAN like repository of submission and testing conventions would even emerge. APIs and test trusses will make it easier for users to submit testing on different platforms in a conventional format, (something the Perl community really mastered, imho). I know it is a way off, but being able to dowload someone's module or contribution, plug it into my sim or even just a test truss and generate consumable test results is just too cool to not hope for someday. Justin, let me know if there is anything I can do to test the testing. ;)<BR><BR>
<DIV class=EC_gmail_quote>On Fri, Aug 29, 2008 at 6:27 PM, Teravus Ovares <SPAN dir=ltr><<A href="mailto:teravus@gmail.com">teravus@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex">
<DIV>OMG ++</DIV>
<DIV> </DIV>
<DIV>Teravus<BR><BR> </DIV>
<DIV><SPAN class=EC_gmail_quote>On 8/29/08, <B class=EC_gmail_sendername>Justin Clark-Casey</B> <<A href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</A>> wrote:</SPAN>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex">In addition to the ideas that MW (and others) have discussed, I'd also<BR>like to put forward the idea of increasing our level of automated unit<BR>and regression tests for the 0.7 release.<BR><BR>Previously I was more in favour of pushing forward quickly rather than<BR>spending too much time test writing (and I think this was how it was<BR>when I joined the project). However. we're now approaching the point<BR>where a reasonable amount of functionality has been filled out in<BR>OpenSim (at least from the Second Life POV). Greater reliability is<BR>going to be necessary if the platform is going to be used seriously for<BR>grid and enterprise level activity. Naturally, there's a level of<BR>self/company-interest here ;-) but I think that spending time on this<BR>will benefit many if not all of us.<BR><BR>Of course, automated tests certainly won't be a perfect safety net but<BR>hopefully it would help to improve OpenSim by catching the revisions in<BR>which regressions are introduced. This will also mean refactoring will<BR>be much less error prone. I'm most probably preaching to the choir here.<BR><BR>I think that part of this will mean pushing the test results from builds<BR>into the IRC channel (as already discussed with Sean), and making test<BR>results more prominent (perhaps even on the <A href="http://opensimulator.org/" target=_blank>opensimulator.org</A> front page?)<BR><BR>Personally, I hope to start putting some of FRI's coding time where my<BR>mouth is and start doing some work towards this this later on next month.<BR><BR>--<BR>justincc<BR>Justin Clark-Casey<BR><A href="http://justincc.wordpress.com/" target=_blank>http://justincc.wordpress.com</A><BR>_______________________________________________<BR>Opensim-dev mailing list<BR><A href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR><A href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR></BLOCKQUOTE></DIV><BR><BR>_______________________________________________<BR>Opensim-dev mailing list<BR><A href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR><A href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></body>
</html>