No subject

Sat Apr 19 01:31:08 UTC 2014

Charles

----- Original Message ----
From: krtaylor <krtaylor at linux.vnet.ibm.com>
To: opensim-dev at lists.berlios.de
Sent: Monday, June 30, 2008 1:41:10 PM
Subject: [Opensim-dev] LSL test suite ideas

I have been putting together a few ideas on how to include more tests 
for LSL. I am thinking of putting together a set of scripts that would 
systematically test all the script functionality that is currently 
implemented. I would start slow with a few functions and grow over time, 
hopefully with others contributions as well. I was thinking I would 
divide the functionality up into logical groups so that it wouldn't be 
too huge and would allow a developer to beat on a specific area if desired.

I know we have used the Kan-Ed scripts in the past but as far as I can 
tell, the Kan-Ed scripts are no more - the Kansas Board of Regents 
closed down the URL for some reason. We could probably piece together 
most of it, but that is not really what I had in mind. The Kan-Ed 
scripts were good for showing a large set worked in world, but I am 
thinking more systematic coverage and reporting. The Kan-Ed scripts 
still required interpretation by someone in world as to whether they 
were working properly or not.

I have had some irc discussions and I think the best approach for now is 
to have a set of scripts that are checked in and exist in inventory that 
can be run in world and would report the success or failure of the 
functions tested. Maybe this report could be pushed out to a webpage for 
on-line status of the current state of the LSL. This would be a 
supplemental  help to me as I  have been manually testing and updating 
the function list and status for several months now.  Additionally, it 
would be nice for putting a load on the script engine for scalability 
and performance testing. There are a few helper os functions that may 
need to be implemented, but the core of what would be tested would be 
done via LSL.

Comments?

-- 
Kurt R Taylor (Kurt Stringer)

Open Virtual Worlds Development
http://opensimulator.org  http://opensim.ibm.com
International Business Machines, Corp.
(512) 838-2496    T/L:  678

_______________________________________________
Opensim-dev mailing list
Opensim-dev at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev

--0-857153825-1214861126=:76701
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;">Dear Kr:<br><br>I think that is a capital idea. I see that we have some scripts in our library. If we had scripts similar to the notion that kan-ed originally used, that is about 10 scripts covering the range from very simple to complex, then we have a series of scripts we can use for testing.<br><br>From time to time, we can then encourage others to add to the test script library as we have additional functionality. The important thing is, I believe, that having such a standard set of scripts again allows is to guide our users to a common level of functionality.<br><br>Charles<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: krtaylor
 <krtaylor at linux.vnet.ibm.com><br>To: opensim-dev at lists.berlios.de<br>Sent: Monday, June 30, 2008 1:41:10 PM<br>Subject: [Opensim-dev] LSL test suite ideas<br><br>
<br>I have been putting together a few ideas on how to include more tests <br>for LSL. I am thinking of putting together a set of scripts that would <br>systematically test all the script functionality that is currently <br>implemented. I would start slow with a few functions and grow over time, <br>hopefully with others contributions as well. I was thinking I would <br>divide the functionality up into logical groups so that it wouldn't be <br>too huge and would allow a developer to beat on a specific area if desired.<br><br>I know we have used the Kan-Ed scripts in the past but as far as I can <br>tell, the Kan-Ed scripts are no more - the Kansas Board of Regents <br>closed down the URL for some reason. We could probably piece together <br>most of it, but that is not really what I had in mind. The Kan-Ed <br>scripts were good for showing a large set worked in world, but I am <br>thinking more systematic coverage and reporting. The Kan-Ed scripts
 <br>still required interpretation by someone in world as to whether they <br>were working properly or not.<br><br>I have had some irc discussions and I think the best approach for now is <br>to have a set of scripts that are checked in and exist in inventory that <br>can be run in world and would report the success or failure of the <br>functions tested. Maybe this report could be pushed out to a webpage for <br>on-line status of the current state of the LSL. This would be a <br>supplemental  help to me as I  have been manually testing and updating <br>the function list and status for several months now.  Additionally, it <br>would be nice for putting a load on the script engine for scalability <br>and performance testing. There are a few helper os functions that may <br>need to be implemented, but the core of what would be tested would be <br>done via LSL.<br><br>Comments?<br><br>-- <br>Kurt R Taylor (Kurt Stringer)<br><br>Open Virtual
 Worlds Development<br><a href="http://opensimulator.org" target="_blank">http://opensimulator.org</a>   <a href="http://opensim.ibm.com" target="_blank">http://opensim.ibm.com</a><br>International Business Machines, Corp.<br>(512) 838-2496    T/L:  678<br><br><br>_______________________________________________<br>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev at lists.berlios.de" href="mailto:Opensim-dev at lists.berlios.de">Opensim-dev at 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></div></div></div></body></html>
--0-857153825-1214861126=:76701--