Simulator Smoke Test

From Second Life Wiki
Revision as of 14:51, 21 March 2018 by Dan Linden (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Setup/Requirements

  • Two user accounts.
  • Three regions.
    • 2 adjacent and 1 remote.
  • One account should be an Estate Manager on the testing region.

Legacy Objects

  • This is needed to test that objects in the old file format (from 2006 and before) still work.
    1. Open your Library/Objects folder.
    2. Rez "Kart 1.0" to the ground.
    3. If it rezzes to the ground then the legacy object updater works.

Mesh Objects

Mesh Upload and Rez

  1. Ensure that you have completed the mesh tutorial for the grid you are testing on
  2. Obtain duck.dae, which is a simple mesh duck
  3. Upload duck.dae, using Build->Upload->Model.. in the viewer
    • Edit the model name to something meaningful, but otherwise keep the default settings
  4. Verify that you are charged L$17 to upload it
  5. Verify that your inventory Objects folder contains a new object with the name you specified
  6. Rez the object from inventory
    • Verify that it loads and appears as to be a duck
    • Select the duck and verify that the Build Tool shows 12 land impact

Mesh Region Crossing

  1. Rez a mesh object near the region boundary. The duck from the upload test is a good choice.
  2. Select the object and move it into the adjacent region using the build tool
  3. Verify that your avatar collides with the object in the new region

Create, save, load, destroy scripts

  • Creating a new script
    1. Open the Statistics Bar from the View menu [or press CTRL-SHIFT-1], and note the # of Active Scripts
    2. Make an object, name it "Spammer", and add the following script to it.
    3. Verify the # of Active Scripts has increased by one.


// Chat spam script
default
{
    state_entry()
    {
        llSetTimerEvent(1);
    }
    timer()
    {
        llWhisper(0, (string)llFrand(1));
    }
    touch(integer num_detected)
    {
       llWhisper(0, "item ID = "+(string)llGetKey());
    }
}


  • Derezzing an object
    1. Take the Spammer into your inventory.
    2. Verify you no longer hear the chat spam.
  • Rez an object into the world from inventory
    1. Rez the Spammer into world again
    2. Verify the script is chatting once per second.
    3. Delete the Spammer
  • Load script from a simstate file on startup [To do this, you need to restart your sim. You will need Estate Manager level access to the region.]
    1. Rez the Spammer
    2. Click the spammer and note the item ID
    3. Note the # of Active Scripts in the Statistics Bar [CTRL-SHIFT-1]
    4. From the Region/Estate window click the Debug tab.
    5. Restart the sim using the "Restart Region" button.
    6. Teleport to another region, then teleport back after the region has restarted.
    7. Verify the Spammer is chatting once per second.
    8. Note the # of Active Scripts is the same as before the sim was restarted.
    9. Click the spammer and verify the item ID is the same as before.
  • Rez an attachment from inventory
    1. Attach the Spammer to your avatar from your inventory.
    2. Verify the script is chatting once per second.
  • Derezzing an attachment
    1. Detach the Spammer by right clicking it in your inventory, and detach.
    2. Verify you no longer hear the chat spam.
  • On an agent teleporting
    1. Attach the Spammer to your avatar from your inventory.
    2. Teleport, and verify the script is chatting once per second. (If it's not, make sure you are in over script enabled land)
    3. Detach the Spammer back to inventory
  • Duplicating an object in-world
    1. Dupe the object by editing it and hitting ctrl-D. Rename the duplicate to "dupe".
    2. Verify both objects are chatting.
    3. Delete the "dupe" object.
  • Deleting a script from an object
    1. Edit the "Spammer" and delete the script from the contents.
    2. Verify you no longer hear the chat spam.
    3. Delete the "Spammer" object.
  • On an object crossing a region boundary
    1. Rez the Spammer near a region boundary
    2. Open the Statistics Bar, and note the # of Active Scripts
    3. Drag the object into the next region
    4. Verify the # of Active Scripts decreased by one.
    5. Verify the Spammer is still spamming
    6. Drag the object back into the region you are in
    7. Verify the # of Active Scripts increased by one.
  • On an attachment/vehicle crossing a region boundary
    1. Rez the Spammer near a region boundary and rename it "Car"
    2. Sit on the Car
    3. Attach the Spammer from your inventory
    4. Verify both objects are spamming.
    5. Drag the Car into the adjacent region.
    6. Verify both objects are still spamming.
    7. Delete the Car
  • Running on an object entering/exiting a no-scripts area
    1. Rez the Spammer near a parcel that is set to "No Outside Scripts"
    2. Open the Statistics Bar from the View menu, and note the # of Active Scripts
    3. Drag the object into the "No Outside Scripts" parcel
    4. Verify the # of Active Scripts does not change
    5. Verify the Spammer stopped spamming
    6. Drag the object back out of the "No Outside Scripts"
    7. Verify the # of Active Scripts does not change
  • Running on a vehicle/attachment entering/exiting a no-scripts area
    1. Rez the Spammer near a parcel that is set to "No Outside Scripts" and rename it "Car"
    2. Sit on the Car
    3. Attach the Spammer from your inventory
    4. Verify both objects are spamming.
    5. Drag the Car into the no script parcel.
    6. Verify both objects have stopped spamming.
    7. Drag the Car out of the no script parcel.
    8. Verify that both objects have resumed spamming.
    9. Delete the Car and detach the spammer.
  • Stop a script on an object
    1. Rez the Spammer
    2. Note the # of Active Scripts in the Statistics Bar
    3. Edit the script on the spammer and uncheck the Running box.
    4. Verify the # of Active Scripts decreased by one.
  • Start a script on an object
    1. Edit the script on the spammer and check the Running box.
    2. Verify the Spammer resumed spamming and the # of Active Scripts increased by one.
    3. Delete the spammer.
  • Drop a script into an object in-world
    1. Rez the Spammer, edit the spammer and drag the script from the Spammer's contents to your inventory.
    2. Note the # of Active Scripts in the Statistics Bar
    3. Delete the script from the Spammer.
    4. Verify the Spammer stopped spamming and the # of Active Scripts decreased by one.
    5. Drag the script from your inventory to the Spammer object.
    6. Verify the Spammer resumed spamming and the # of Active Scripts increased by one.
  • Compiling a script successfully
    1. Note the # of Active Scripts in the Statistics Bar
    2. Make a box, add the default script, and save it.
    3. Verify the # of Active Scripts increased by one.
  • Failing to compile a script
    1. Edit the script, change "default" to "defaul" and save it.
    2. Verify the # of Active Scripts decreased by one.
    3. Delete the box

XML-RPC testscript

Oskar update this section


Teleport

  • Teleport within the same region
  1. Attach the popgun from the Library.
  2. Teleport to another location within the same region.
  3. Verify the teleport is quick and all your attachments arrive.
  • Teleport to a far, non-adjacent regions (that doesn't have a child agent)
  1. Teleport to a region that is not adjacent to the sim you're in.
  2. Verify all your attachments arrive.
  • Teleport to an adjacent region
  1. Walk up to sim boundary, but don't walk across it. Teleport across the boundary to the other region.
  2. Verify all your attachments arrive.
  • Users cannot teleport onto parcels they are banned from
  1. Ban a test account from a parcel you own.
  2. With the test account, attempt to teleport onto the parcel.
  3. Verify the test account arrives at a parcel that is nearby the parcel they are banned from.
  • Users can teleport others to their location bypassing telehubs and landing points.
  1. Put your User A on an island that has a Telehub and a Landing point, then move away from the landing point. (try Bug Island - http://slurl.com/secondlife/Bug%20Island/150/150/30)
  2. Have User A search for User B a and offer a teleport.
  3. Have User B accept the teleport offer. (User B should not be an estate manager for the region)
  4. Verify that User B arrives in front of and facing User A.
  • Users can teleport to their friend's location
  1. Have User A and User B befriend each other. In the Friend list, click the button to allow the other to see your location on the map.
  2. Have User B teleport away.
  3. Have User B, open User A's Profile, click Show on Map, then teleport to that location.
  4. Verify that User B arrives at the region's telehub, and a red beacon is highlighting the User A's position.

llHTTPRequest test

  1. Add the following script to an object and verify the script says "http test passes".
key my_http_request;
string http_url="http://www.google.com";
default
{
    state_entry()
    {
        //llSay(0, "http test start");
        my_http_request = llHTTPRequest(http_url, [] ,"");
    }
 
    http_response(key id,integer status, list meta, string body)
    {
        if(my_http_request == id)
        {
           llSay(0, "http test passes");
        }
    }   
}


Region handoffs

  • Region handoffs and attachments
  1. Wear the Popgun from the Inventory Library.
  2. Enter mouselook and verify the popgun fires. (if it fails, make sure you're on a parcel that allows running scripts and rezzing objects)
  3. Edit the popgun, and move it away from your hand.
  4. Fly across a region boundary.
  5. Verify the popgun is still positioned away from your hand.
  6. Enter mouselook and verify the popgun still fires.
  • Region handoffs while sitting.
  1. Rez the Kart from the inventory and sit on it.
  2. Drive into another region.
  3. Verify you are sitting in the same position, and your avatar is playing the same sit animation.
  4. Verify the Kart still has your controls and you are able to drive it.


Run physics. Rez, derez, link, delink, handle collisions, etc.

  • Link and delink retains positions and rotations of prims.
  1. Make a complicated linked object with more than three pinned primitives, each piece with a non-trivial rotation, and preferably not all the same shape:
  2. Unlink and link the collection a few times... the primitives should not change position/rotation between link/unlink cycles.
  3. Duplicate the linked object with ctrl-D. Verify the copy looks the same as the original.
  • Throwing objects across region boundaries
  1. Set the linked object physical and use Grab to throw it around. Verify it collides with the ground correctly.
  2. Throw the object across the region boundary. Verify that it crossed the region boundary correctly.
  3. Grab the same object in the remote region, and drag it back into your avatar's region. Verify it collides with the ground correctly.
  • Prim Fights
  1. Create two boxes at the same position.
  2. Select both boxes and set them physical
  3. Verify that one box slowly moves above the other box, and rests on top of it with a small gap.

Pathfinding

Basic Navmesh Generation

  1. Login to a region
  2. Open Build->Pathfinding->View/Test in the viewer, and enable the 'Navmesh' option to view the current navmesh of the region
  3. Rez a box several meters above the ground, and scale it to be 30m * 30m, making it a large platform
  4. Open the 'Pathfinding Linksets' floater in the viewer, and set your platform to be "Walkable". Apply this change.
  5. Hit Build->Pathfinding->Rebake Region to regenerate the navmesh
  6. After a minute or so, verify that the navmesh has been updated, in the "Pathfinding view/test" floater
    • The platform should appear in the navmesh
    • The navmesh should otherwise appear as it did before you added the platform

Basic Character Movement

  1. Rez a box on a walkable surface, such as the platform created in the previous test
  2. Save this wandering character script in the box
  3. Select the box, and verify that the build tool shows this in the General tab:
    • Pathfinding attributes: character
    • land impact 15 (this is derived from the fixed physics cost of 15 for pathfinding characters)
  4. Touch the box, and verify that it wanders around the nearby area

Cross Region Pathfinding

  1. Find a region border which is amenable to object crossing
    • Parcels on both sides of the region boundary allow scripts and object entry for everybody
    • Reasonably flat terrain around the region border
    • If you change any settings which would affect the navmesh, rebake the navmeshes and wait a minute for the regions to share navmeshes
  2. Rez a box on the ground, close to the region border
  3. Save this wandering character script in the box
  4. Select the box, and verify that the build tool shows this in the General tab:
    • Pathfinding attributes: character
    • land impact 15 (this is derived from the fixed physics cost of 15 for pathfinding characters)
  5. Touch the box to initiate pathfinding movement
  6. Verify that the box (eventually) wanders into both regions. The destinations chosen by the box should be within the area specified by the script.

Script and URL limit reporting

  • Requires a viewer that supports script limits (e.g. viewer2)
  1. Go to a parcel you do not own (and not owned by a group that you own)
  2. In a viewer that supports script limits (e.g. viewer2), select the parcel and open "About Land"
  3. Verify that the "About Land" floater has a visible "Script Info" button
  4. Click on the "Script Info" button, and note the total memory and URLs used in the parcel. Also verify that individual scripted items are *not* listed.
  5. Rez a box in the parcel, and name it "WWW Server"
  6. Save the "www server" script (shown below) in "WWW Server" as Mono
  7. The WWW Server should supply you with a URL. Verify that you can visit this URL in a browser, and browser shows "Hello World!"
  8. Refresh the Script Info floater while selecting the parcel, and verify that the URLs usage increases by 1, and that the script memory usage increases by 64KB. Also verify that individual scripted items are *not* listed.
  9. Open the "My Avatar" tab on the Script Info floater, and verify that "WWW Server" appears in the list of scripted items, at "Location: Right Hand". Verify that it's still using 64KB of memory and 1 URL.
  10. Detach "WWW Server"
  11. Refresh list of items under the Script Info floater's "My Avatar" tab. Verify that "WWW Server" no longer appears in the list, and that your avatar's memory and URL usage decreased by 64KB and 1 URL, respectively.

Script: www server

default
{
   on_rez(integer reznum)
   {
       llResetScript();
   }
   attach(key id)
   {
       if(id!=NULL_KEY) llResetScript();
   }
   state_entry()
   {
       llRequestURL();
   }

   http_request(key id, string method, string body)
   {
       if (method == URL_REQUEST_GRANTED)
       {
           llSay(0,"URL: " + body);
       }
       else if (method == URL_REQUEST_DENIED)
       {
           llSay(0, "Something went wrong, no url. " + body);
       }
       else if (method == "GET")
       {
           llHTTPResponse(id,200,"Hello World!");
       }
       else
       {
           llHTTPResponse(id,405,"Unsupported Method");
       }
   }
}


Camera avatar-anti-occlusion (Keep your avatar visible)

  • Camera should move to keep your avatar in view, but should not oscillate.
  1. Create a 10x10x10m prim.
  2. Back up to the 10x10x10m prim. Verify the camera dollies in until it's right above your head.
  3. Create a 10x01x10m prim wall.
  4. Back up to a 10x01x10m wall. Verify your camera stays on the same side of the wall as the avatar, and does not pop through to the other side.
  5. Stand back to back with an avatar that is the same height as you. Verify the camera does not bob around or zoom in and out repeatedly.
  • Phantom object have no effect on the camera.
  1. Test: Walk through a 10x10x10m Phantom box. Verify your camera follows your avatar through the box without any automatic dollying.


Object Selection management

  • Selection order is maintained when linking objects
// Link number script
default {
    state_entry() { }
    changed(integer what_changed) {
        if (what_changed & CHANGED_LINK)
        {
            llSetText("Link #" + (string)llGetLinkNumber(), <1,.5,0>,1 );
        }
    }
}
  1. Create a box on the ground and add the above script to the box. (Click the Content tab, click New Script, open the script, replace the script text with the following script text, click Save)
  2. Duplicated the box 2 times so you have 3 boxes.
  3. Enter edit mode, Ctrl-3.
  4. Shift-click each of the boxes (from left to right) to select them.
  5. Link the boxes by hitting Ctrl-L.
  6. Verify the first box you selected is Link #3, and the last box you selected is Link #1.
  7. Unlink the object by hitting Ctrl-Shift-L.
  8. Link the boxes again by hitting Ctrl-L.
  9. Verify the link order is the same as before.
  10. Unlink the object again. (Ctrl-Shift-L)
  11. Shift-click the middle prim to deselect it, then shift-click it to select it again.
  12. Link the boxes again by hitting Ctrl-L.
  13. Verify the link numbers from left to right are #3, #1, #2.
  14. Unlink and deselect the boxes.
  • Drag select selection order matches shift select order
  1. Enter edit mode, Ctrl-3.
  2. Drag-select the ground around the 3 boxes from right to left.
  3. Link the boxes.
  4. Verify the link numbers from left to right are #1, #2, #3.
  5. Unlink the boxes and click the ground to deselect them.
  • Collection of prims remain selected after rez
  1. Enter edit mode, Ctrl-3.
  2. Shift-click each of the 3 boxes to select them (order isn't important).
  3. Right-click one of the boxes and choose Take.
  4. Remain in edit mode, open your inventory, find the object you took, and rez it.
  5. Verify all prims remain selected.
  • Object remains selected after rez
  1. Link the 3 boxes by hitting Ctrl-L.
  2. Remaining in edit mode, take the object to inventory, then rez it again.
  3. Verify all prims remain selected.
  • Your attachments remain selected after being dropped.
  1. Right-click your attachment and Wear it.
  2. Now, Drop it.
  3. Verify the dropped attachment remains selected even after walking around with the arrow keys.
  • You cannot edit other people's attachments.
  1. Enter edit mode, Ctrl-3.
  2. Click another person's attachment.
  3. Verify you cannot modify the attachment either by dragging it nor via the Edit tools window.
  • Objects retain selection when dragged across a region boundary.
  1. Edit an object and drag it across a region boundary, then release.
  2. Verify the object remains selected and you are able to change its properties (eg. color).


Terrain Selection management

  • Right-click About Land selects the entire parcel.
  1. Right click a parcel and choose About Land from the pie menu.
  2. Verify a yellow "fence" surrounds the entire parcel.
  3. Verify the About Land window displays the Owner of the parcel.
  • Edit Terrain, then drag selects part of a parcel.
  1. Right click the terrain and choose Edit Terrain from the pie menu.
  2. Left-click and drag on the terrain to select a rectangle of land.
  3. Verify a rectangular yellow "fence" highlights the area you selected.


Parcel ownership. Divide, join, sell, deed, access, media, music

  • Sell and buy a parcel.
  1. User A sets a parcel for sale to anyone.
  2. User B purchases the parcel.
  3. Verify the parcel turns green and says User B is the owner in About Land.
  • Divide your parcel
  1. Right click the terrain and choose Edit Terrain from the pie menu.
  2. Turn on show Parcel Owners.
  3. Left-click and drag on the terrain to select a portion of your parcel.
  4. Click the Subdivide button in the Edit Terrain tools.
  5. Verify your parcel has its own border now.
  6. Verify the parcel's name, description, and owner remained the same.
  • Join two parcels
  1. Enter Edit Terrain mode
  2. Left-click and drag on the terrain to select two or more of your parcels.
  3. Click the Join button in the Edit Terrain tools.
  4. Verify the parcel border has updated to show all the parcels are now one parcel.
  • Deed the parcel.
  1. Open the About Land window for your parcel.
  2. In the General tab, set the parcel's group to one of your groups for which you have ability to buy land (usually officer or owner)
  3. Check the Allow Deed and Make Contribution boxes
  4. Click the Deed button and confirm.
  5. Verify the parcel info now says group owned, and indicates which group owns it.
  6. Verify the parcel overlay is teal in color.
  • Parcel access
  1. With User A, open the About Land window for a parcel owned by you, choose the Access tab, and add User B to the ban list.
  2. User B, attempt to enter the parcel.
  3. Verify that User B sees a red "No Entry" wall and is bounced back from the parcel edge.
  4. With User A, unban User B.
  5. Verify that User B can once again enter the parcel.
  • Media
  1. With User A, open the About Land window for a parcel owned by you, choose the Media tab, and set the media URL to https://s3-us-west-2.amazonaws.com/lecs-bugislandtests/texture_cell_animation.mov
  2. Verify the Media type on the About Land tab changes to "Movie - video/quicktime"
  3. Set the media URL to http://lindenlab.com
  4. Verify the Media type on the About Land tab changes to "Web content - text/html"
  5. Set the media URL to https://lindenlab.com
  6. Verify the Media type on the About Land tab changes to "Web content - text/html"
  • Music
  1. With User A, acquire a streaming music URL. You can get one from shoutcast.com. (Click a "tune in" button, save the .pls file, and snag a URL from it). This URL worked fine for me last time: http://205.188.215.229:8040
  2. Open the About Land window for a parcel owned by you, choose the Media tab, and set the music URL.
  3. Verify you hear the music when you are on the parcel, and verify the music turns off when you leave the parcel.

Object return

  • Return objects due to time limit
  1. Tester 1: Buy one 16m2 parcel of land.
  2. Tester 1: Right click on the parcel -> select About Land from pie menu.
  3. Tester 1: Goto the Objects tab of About Land window -> set Autoreturn other user's objects to 1 minute.
  4. Tester 2: Rez 1 box on Tester 1's parcel.
  5. Tester 2: Wait 1 minute. Verify that Tester 2's object has been returned to inventory.
  • Return objects due to parcel owner manually returning land objects
  1. Tester 1: Right click on your land parcel -> then select About Land from pie menu.
  2. Tester 1: Goto the Objects tab of About Land window -> set Autoreturn other user's objects to 0 minute.
  3. Tester 2: Rez 1 box on Tester 1's parcel.
  4. Tester 1: Right click on the parcel => select About Land from pie menu.
  5. Tester 1: Goto the Objects tab of About Land window -> click on the "Return Objects" button next to the "Owned by others:" dialogue.
  6. Tester 2: Verify object was returned to Tester 2.


Voice options

  • Voice options. Requires User A to be an Estate Manager.
  1. Move User A and User B near each other and communicate with the spatial voice option on a parcel owned by User A.
  2. With User A, turn off the parcel's voice option.
  3. Verify voice no longer works on the parcel.
  4. With User A, turn on the parcel's voice option
  5. Verify voice works again.
  6. With User A, turn off the Estate's voice option.
  7. Verify voice no longer works on the estate.
  8. With User A, turn on the Estate's voice option.
  9. Verify voice works again.
  10. Verify voice works in a person to person IM session.
  11. Verify voice works in a group IM session.
  12. Verify voice works in a conference IM session.


Chat

  1. Chat with each other
  2. Verify chat is showing correctly in the console


Instant Message system

  • Person to person IM.
  1. Teleport User A to a different region than User B.
  2. Have the User B IM User A.
  3. Verify you can IM back and forth.
  • Group IM
  1. Have User B start a group IM with User A.
  2. Verify you can IM back and forth.
  • Conference Chat IM
  1. With User B, create a folder in your Calling Cards folder.
  2. Copy and paste User A's calling card into the folder you created.
  3. Right click the new folder and start a Conference IM
  4. Verify you can IM back and forth.
  • Inventory offer
  1. With User B, drop an object onto User A's calling card.
  2. Have User A accept and open the object.
  3. Verify the object rezzes correctly.
  • Money transactions
  1. Have User A open the User B's profile and Pay them L$1.
  2. User A, verify your balance decreased by L$1.
  3. User B, verify your balance increased by L$1.


Presence

  • Online Friends
  1. Make the users Friends if they are not already.
  2. Log User A out, and verify that User B sees the correct online status in the Friends list.
  3. Log User A into a region non-adjacent to the region the User B is standing in. Verify both users see the correct online status in the Friends list.

Group Invite

  1. Create a new group
  2. Invite one friend to the group
  3. Invite one non-friend to the group
  4. Invitees accept group invitation and relogin
  5. Invitees see that the new group is on their list

Sim cached assets

  1. User B, enter appearance, change you skin color, then save and exit appearance mode.
  2. Teleport User B to the User A's location.
  3. Verify that User B sees the correct skin color on User A.


Login: Location, New Location

  1. Move to a new location near where you started that you can remember.
  2. Logout of SL, Restart the SL Application, but don't login.
  3. Click the "Preferences" Button on the Login Screen
  4. Set/Check the General->Login Location to "My Last Location", Click "Apply" and "Ok"
  5. Click "Log In" to Connect to SL
  6. Verify you are in the location where you logged off.


Search

  1. Have User B open Search and search for User A.
    1. Verify that User B can see the User A's profile.
  2. From the profile double click on a group name.
    1. Verify that User B can see the group info.
  3. Search Classifieds for "hair"
    1. Verify you get a result.
    2. Change the maturity content from PG, to M, to A.
    3. Verify you get different result.
  4. Search Places for "oatmeal"
    1. Verify you get a result.
    2. Change the maturity content from PG, to M, to A.
    3. Verify you get different result.


Buying an object

  1. User B, create a box and set it for sale, Copy, for L$3.
  2. User A, buy the box.
  3. Verify the balances were correctly changed by L$3.


Estate tools

  1. UserA, who is an estate manager or region owner: Go to a region which belongs to your estate
  2. UserB: Go to a different region which belongs to the same estate
  3. UserA: Add UserB to the "Banned residents" list under World->Region/Estate->Estate
  4. UserB: Verify that you are ejected from the region within seconds, and teleported home
  5. UserB: Attempt to TP to the region you were just ejected from, and verify that this is prevented due to the estate ban.
  6. UserA: Remove UserB from the "Banned residents" list in Estate Settings.
  7. UserB: Verify that you can return to the region you were ejected from.

Object permissions

  1. User A, create a box and set it to "Anyone can copy"
  2. User B, right click the box and take a copy.
  3. Verify the object says (no modify)(no copy) in your inventory.
  4. User B, rez the box.
  5. Verify the box was removed from your inventory.
  6. User B, attempt to modify the size of the box, and make a copy of the box.
  7. Verify you cannot modify or copy the box.
  8. Delete the 2 boxes.


Email test in and out of the grid

  1. User A, add the following script in a box, and insert your email address in the first line of the script.
  2. Click the box, check your email - verify that the email is received.
  3. (no aditi) Reply to the email.
  4. (no aditi) Verify the box says "Received email:" etc. (expected to be disabled on aditi)
string emailaddress = "YOUR-EMAIL-ADDRESS";
list m;
default
{
    state_entry()
    {
        llOwnerSay("ready. My key is "+(string)llGetKey());
        llSetTimerEvent(1);
    }
    touch_start(integer total_number)
    {
        llOwnerSay("sending email to "+emailaddress+" ...");
        llEmail(emailaddress,"llEmail test. please reply.",(string)llFrand(1));
        llOwnerSay("email sent. please reply to the email.");
    }
    timer()
    {
        llGetNextEmail("","");
    }
    email(string time, string from, string subj, string mes, integer remaining)
    {
        m = llParseString2List(mes,["\n",":"],[]);
        llOwnerSay("Received email:"+llDumpList2String(llList2List(m,7,-1),":"));
        if (remaining > 0) llGetNextEmail("","");
    }
}

Display Names

  1. make sure you have a display name set
  2. create a new prim on the ground
  3. put this script into the prim.
  4. touch the prim a few times.
  5. verify that it shows your display name
key touched_id;
key touched_query;
string touched_name;
default
{
    state_entry()
    {
        llSetText("Touch Me!",<1,1,1>,1.0);
    }
    
    touch_start(integer a)//Announce who touched
    {  
        touched_id=llDetectedKey(0);
        touched_query=llRequestDisplayName(touched_id);
        touched_name = llGetDisplayName(llDetectedKey(0));
    }
    dataserver(key queryid, string data)
    {
        if(touched_query==queryid)
        {
            if(touched_name==data)
            {
                llSay(0,touched_name + " touched me "+ " (" + llGetUsername(touched_id) + ")");
            }
            else
            {
                llSay(0,"ERROR: Mismatch: llRequestDisplayName() returned \'"+data+"\', llGetUserName() returned \'"+touched_name+"\'");
            }
        }
        else
        {
            llSay(0,"ERROR: unrecognized query ID "+(string)queryid);
        }
    }
}


Snapshot Email, Save and Basic Image Upload

  1. In-world click on Snapshot Icon
    1. Verify that snapshot looks ok
    2. Click on Send Via Email
    3. Fill out form and submit
    4. Verify that email with snapshot is received
  2. In the Snapshot window, click on "Save to Disk"
    1. Save a 512x512 jpeg image to your desktop
    2. Verify the image looks ok in a photo viewer
  3. Click Build / Upload / Image menu
    1. Select the image you just saved
    2. Upload preview should open up shown that image
    3. Select "Upload (L$10) and upload (assuming you have L$ available)
    4. Notification about paying L$10 should appear
    5. Inventory window should open to show the new uploaded image
    6. Double click on the new image in inventory
    7. Verify image viewer opens and shows the correct picture

Experience Tools

  1. Obtain Experience Key Viewer (http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers)
  2. Login with a user that owns an Experience (Grid Scope on Aditi)
  3. Rez an object and add the following script
key agent=NULL_KEY;
integer anim=1;
default
{
   state_entry()
   {
       llSetText(llGetObjectName(), <1.0, 1.0, 1.0>, 1);
   }
 
   touch_start(integer total_number)
   {
       if(agent)
       {
           if(anim==1)
           {
               llStopAnimation("sleep");
               llStartAnimation("sit");
           }
           else
           {
               llStopAnimation("sit");
               llStartAnimation("sleep");
           }
           anim = 1-anim;
       }
       else
       {
           llRequestExperiencePermissions(llDetectedKey(0), "");
       }
   }
    
   experience_permissions(key a)
   {
       llSay(0, "Got perms for "+(string)a);
       agent = a;
   }
    
   experience_permissions_denied(key a, integer reason)
   {
       llSay(0, "No perms for "+(string)a+" "+llGetExperienceErrorMessage(reason));
       agent = NULL_KEY;
   }
}
  1. In the script window, check Experience box
  2. Assign the Experience from the drop down menu
  3. Save the script
  4. Open Experience Profile for the Experience [>]-button
  5. Click Forget button (if active)
  6. Click on the object
  7. Confirm a dialog requests your participation in an experience.
  8. Click Yes to grant permissions.
  9. Click the object a few times and confirm your avatar toggles between Sit and Sleep animations.
  10. Open the Experience profile for the Experience and click the Block button.
  11. Click on the object again
  12. Confirm you see a message: No Perms for $AgentID operation not permitted
  13. Confirm your avatar does not change animations.