<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>Hi Gerikes</SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG> </DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>I only can agree with you about code quality and esp.
stability after unit tests are introduced.</SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG> </DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>I started working on introducing unit tests to the
meshing code. Nono of that is currently in the repository although I have most
of that code under test.</SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>I will carry that on when the pre-Christmas stress has
ebbed away in (hopefully) a week from now. </SPAN></FONT></STRONG><STRONG><FONT
face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>Other plans are a test framework for the physics engine
that allows to replay reproducable
situations.</SPAN></FONT></STRONG></DIV></SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG> </DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>Definitely interested in this
issue.</SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG> </DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007></SPAN></FONT></STRONG> </DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>best regards and happy
christmas</SPAN></FONT></STRONG></DIV>
<DIV dir=ltr align=left><STRONG><FONT face=Arial color=#0000ff><SPAN
class=615321707-17122007>Gerhard</SPAN></FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial color=#0000ff></FONT></STRONG> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2><BR> </FONT>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Von:</B> opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <B>Im Auftrag von
</B>Gerikes<BR><B>Gesendet:</B> Samstag, 15. Dezember 2007 18:54<BR><B>An:</B>
Opensim-dev@lists.berlios.de<BR><B>Betreff:</B> [Opensim-dev] Automated
Testing<BR></FONT><BR></P>
<DIV></DIV>Hi all.<BR><BR>Just starting to look at this project, and seems
interesting enough. I come from a short background creating internal corperate
web sites using C# / Monorail, but have interests in virtual worlds, and am
happy to see such a project being built on .NET. <BR><BR>Anyway, I've been using
automated unit and integration testing for almost a year now, and found it
drastically increased the quality of my code. What is the position of the
project in terms of how unit testing are implemented? Does anyone on the project
write their own but just not commit them? <BR><BR>I'd be hasty to try to come in
here trying to change the world (so to speak), so perhaps I'll start smaller.
I'm planning on trying to grok the code base by developing my own test harness
that can be used for integration testing. Basically, it would be a region that
could be started, and have tests run against it, probably in the form of sending
commands through bots connected using libsecondlife. The API would allow for the
tests to run multiple times, perhaps switching out things like which data store
manager is used during the test so that a single test can be run against
multiple implementations. <BR><BR>I would try to allow the creation of tests to
be simple and straightforward, such as...<BR><BR><BR>[Test]<BR>public void
CanInstantMessage()<BR>{<BR>const string message = "Test
Message";<BR><BR>TestAvatar avatar1 = ActivateNewAvatar(); <BR>TestAvatar
avatar2 = ActivateNewAvatar();<BR>avatar1.Perform(Action.InstantMessage(avatar2,
message));<BR><BR>Assert.AreEqual(1,
avatar2.RecievedMessages.From(avatar2).Count);<BR>Assert.AreEqual(message,
avatar2.RecievedMessages.From (avatar2).First().Message);<BR>}<BR><BR>So that's
it, I'm interested in any feedback you
have.<BR><BR><BR><BR><BR><BR><BR><BR></BODY></HTML>