Difference between revisions of "Aditi/ThouMustNotFail"

From Second Life Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by 3 users not shown)
Line 2: Line 2:
== Synopsis ==
== Synopsis ==
This is a list of the most critical resident created objects used in Second Life that need to always work.  
This is a list of the most critical resident created objects used in Second Life that need to always work.  
== The Reasoning ==  
== The Reasoning ==  
Second Life is very complex. There are an infinite number of ways to do things in Second Life. These methods may be right or wrong. These methods may exploit bugs or logic holes. While testing upcoming server releases it just isn't possible to test everything resident created. QA will test changed features and make sure they work as expected. Oftentimes there are edge cases that fail without QA's knowledge. This list is a list of really important items that should always work. We will test these objects early on in the QA process and use it as a sort of canary in the coal mine test.
Second Life is very complex. There are an infinite number of ways to do things in Second Life. These methods may be right or wrong. These methods may exploit bugs or logic holes. While testing upcoming server releases it just isn't possible to test everything resident created. QA will test changed features and make sure they work as expected. Oftentimes there are edge cases that fail without QA's knowledge. This list is a list of really important items that should always work. We will test these objects early on in the QA process and use it as a sort of canary in the coal mine test.
= Vendors =
= Vendors =
* Apez iServ
* Hippo technologies products (hippo rent and hippo vend)
* Hippo technologies products (hippo rent and hippo vend)
* Metalife related vendors and servers objects.
* Quantum Products Vending and Rack Servers
* XStreet SL Server Objects
* XStreet SL Server Objects
* Metalife related vendeors and servers objects.


= Land Management Tools =
= Land Management Tools =
Line 16: Line 20:
* Posjump things
* Posjump things
* Flight Feathers
* Flight Feathers
* WarpPos. https://wiki.secondlife.com/wiki/WarpPos
* Dynamic avatar sit target. <code>[[llSetLinkPrimitiveParams]]([[llGetNumberOfPrims]](), [<nowiki></nowiki>[[PRIM_POSITION]], <50, 0,0>]);</code>
* Regular 300m sit target. <code>[[llSitTarget]](<300,300,300>, [[ZERO_ROTATION]]);</code>
= Web =
* Transaction History Page (used by vendors to validate payments)
= Viewer =
* Alpha on HUDs to render the same as in world (broken by 1.23 {{Jira|VWR-13151}})
* Content to render the same between viewer versions. eg: 1.x and 2.0
= DEBUG =
* [[DEBUG CHANNEL|Debug Channel]] number and data sent to remain consistent (used for auto script repair)

Latest revision as of 17:07, 13 March 2010

Thou Must Not Fail

Synopsis

This is a list of the most critical resident created objects used in Second Life that need to always work.

The Reasoning

Second Life is very complex. There are an infinite number of ways to do things in Second Life. These methods may be right or wrong. These methods may exploit bugs or logic holes. While testing upcoming server releases it just isn't possible to test everything resident created. QA will test changed features and make sure they work as expected. Oftentimes there are edge cases that fail without QA's knowledge. This list is a list of really important items that should always work. We will test these objects early on in the QA process and use it as a sort of canary in the coal mine test.

Vendors

  • Apez iServ
  • Hippo technologies products (hippo rent and hippo vend)
  • Metalife related vendors and servers objects.
  • Quantum Products Vending and Rack Servers
  • XStreet SL Server Objects

Land Management Tools

  • objects which ban/kick users
  • automated parcel rental systems

Physics

Web

  • Transaction History Page (used by vendors to validate payments)

Viewer

  • Alpha on HUDs to render the same as in world (broken by 1.23 VWR-13151)
  • Content to render the same between viewer versions. eg: 1.x and 2.0

DEBUG

  • Debug Channel number and data sent to remain consistent (used for auto script repair)