Difference between revisions of "Quality Assurance Testing Format"
| Line 7: | Line 7: | ||
'''[VERSION] 0.1''' This is the version number for this test script. | '''[VERSION] 0.1''' This is the version number for this test script. | ||
'''[ | '''[DURATION] 00:15''' Time to execute the test. This will be adjusted during Preview as metrics come in. | ||
'''[TESTERS] 1''' Number of testers required to run the test. | '''[TESTERS] 1''' Number of testers required to run the test. | ||
'''[OVERVIEW]''' The overview of the test. | '''[OVERVIEW]''' The overview of the test. | ||
| Line 23: | Line 21: | ||
'''[INV]''' Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed. | '''[INV]''' Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed. | ||
'''[SCRIPT]''' This is where LSL code will be | '''[SCRIPT]''' This is where LSL code will be for the test. | ||
'''[CASE NAME]''' You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here. | '''[CASE NAME]''' You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here. | ||
'''[0010]''' This is a high level test case number. | '''[0010]''' This is a high level test case number. (DEPRECATED) | ||
'''[0010.0010]''' This is a sub - case, an immediate child of 0010. | '''[0010.0010]''' This is a sub - case, an immediate child of 0010. (DEPRECATED) | ||
===Reserved Words and Symbols=== | ===Reserved Words and Symbols=== | ||
Revision as of 06:54, 24 March 2008
Test Script Formatting
[PHYSICSTEST] The name of the test.
[1] The URL of the test.
[VERSION] 0.1 This is the version number for this test script.
[DURATION] 00:15 Time to execute the test. This will be adjusted during Preview as metrics come in.
[TESTERS] 1 Number of testers required to run the test.
[OVERVIEW] The overview of the test.
[SETUP] Instructions and other requirements for the test.
[TEST DATA] Data for the test.
[NOTE] Any other information related to the test, will be expressed at test time with the step that it follows.
[INV] Place the name of any inventory items that are needed for the test here. It will be added to your test and rezzed when needed.
[SCRIPT] This is where LSL code will be for the test.
[CASE NAME] You'll see this below. Sections within our tests often have headings, which contain the case name. They will be contained in braces as seen here.
[0010] This is a high level test case number. (DEPRECATED)
[0010.0010] This is a sub - case, an immediate child of 0010. (DEPRECATED)
Reserved Words and Symbols
[DURATION]
[NOTE]
[OVERVIEW]
[SETUP]
[TESTERS]
[INV]
[SCRIPT]
[*]
As long as the case number is enclosed in braces, it can be parsed. In the future we want to support further sub-casing, up to say, 4 levels. Each sub-case level will be able to sustain up to 9999 parts.
The entire script will be parsed at initialization time, and steps (cases) will be indexed.
Here is a sample test script, properly formatted: Quality Assurance Example Script